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
Once we do this change here for a given resource, Observe Only resources would immediately work without needing all required fields to be provided, whether CEL is available or not. What users with k8s <= 1.24 (without the alpha feature enabled) lose is that when, management policy is not ObserveOnly, they will no longer get a validation error at the API server level, during CR creation when they didn't provide a required field.
This would definitely be a UX degradation; however, it shouldn't be a huge deal assuming the reconciler will report the error from cloud API indicating that a required field is missing.
@haarchri, thanks for the ticket, and sorry for the inconvenience.
Yes, this is expected behavior.
Would adding this information to the provider readme's and in the release notes for the relevant release be sufficient? Do you have other places in mind?
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with/fresh will mark this issue as not stale.
This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!
What problem are you facing?
since #672 is merged - we missing some information in readme about this fact:
crossplane/crossplane#3531 (comment)
for example:
AWS EKS - 1.24 end of support in January 2024
https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html
The text was updated successfully, but these errors were encountered: