You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context
When applying a resource request that exceeds the 63 character limit, the following behaviour occurs:
Kratix attempts to reconcile the resource request
Due to the request name it error when attempting the set the kratix.io/resource-name label
Reconciliation never ends
This is also difficult to recover from as when the deletion timestamp is applies, the reconciler still attempts to parse and set the labels but cannot due to the character limit. Users need to delete the Promise and the kratix.io/resource-request-cleanup finalizer which is less than ideal
Acceptance
Given I have a resource.yaml where the name is greater that 63 characters
When I run kubectl apply -f resource.yaml
Then I am immediately informed that my resource cannot be applied due to the name exceeding 63 characters
And there is no attempt to reconcile the request
The text was updated successfully, but these errors were encountered:
qq: this is just for resource name, we mentioned on the quick chat that it may also be true for container names, is this the case? do we need a second task for that?
thanks :)
qq: this is just for resource name, we mentioned on the quick chat that it may also be true for container names, is this the case? do we need a second task for that? thanks :)
Context
When applying a resource request that exceeds the 63 character limit, the following behaviour occurs:
kratix.io/resource-name
labelThis is also difficult to recover from as when the deletion timestamp is applies, the reconciler still attempts to parse and set the labels but cannot due to the character limit. Users need to delete the Promise and the
kratix.io/resource-request-cleanup
finalizer which is less than idealAcceptance
Given I have a
resource.yaml
where thename
is greater that 63 charactersWhen I run
kubectl apply -f resource.yaml
Then I am immediately informed that my resource cannot be applied due to the name exceeding 63 characters
And there is no attempt to reconcile the request
The text was updated successfully, but these errors were encountered: