• Justin Santa Barbara's avatar
    AWS: Fix cleanup of security group · c2caa3f1
    Justin Santa Barbara authored
    The most reliable way seems to be to deauthorize the LB security group from
    other groups, then delete the LB itself, then repeatedly retry to delete the LB
    security group.
    
    We can't delete the LB security group until the LB is actually completely
    deleted, but the LB is hidden from the API during deletion.  So our only real
    option is to retry deletion of the LB security group until the expected error
    goes away when the LB is fully deleted.
    c2caa3f1
Name
Last commit
Last update
..
admission Loading commit data...
api Loading commit data...
apiserver Loading commit data...
auth Loading commit data...
capabilities Loading commit data...
client Loading commit data...
clientauth Loading commit data...
cloudprovider Loading commit data...
config Loading commit data...
controller Loading commit data...
conversion Loading commit data...
credentialprovider Loading commit data...
fieldpath Loading commit data...
fields Loading commit data...
healthz Loading commit data...
httplog Loading commit data...
hyperkube Loading commit data...
kubectl Loading commit data...
kubelet Loading commit data...
labels Loading commit data...
master Loading commit data...
namespace Loading commit data...
probe Loading commit data...
proxy Loading commit data...
registry Loading commit data...
resourcequota Loading commit data...
runtime Loading commit data...
securitycontext Loading commit data...
service Loading commit data...
serviceaccount Loading commit data...
tools Loading commit data...
types Loading commit data...
ui Loading commit data...
util Loading commit data...
version Loading commit data...
volume Loading commit data...
volumeclaimbinder Loading commit data...
watch Loading commit data...