-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How frequently the controllers are patched with new fetures released by the respective services? #2071
Comments
Since we generate the controllers this is a relatively easy task to do. If the service feature is just a field, we can regenerate the controllers, run the tests and ship a release in around an hour. If the feature is more of a new resource (e.g IAM Role) this can take up to a few hours or couple days to support. |
I went through the https://aws-controllers-k8s.github.io/community/docs/community/services/ and saw that many services are in the PREVIEW stage. One of them is Amazon Route 53 RELEASED PREVIEW 0.0.12 When you say the controllers are patched immediately, do you mean for services that are already in the General Availability stage? is this (https://aws-controllers-k8s.github.io/community/docs/community/services/) the right place to know if a service is in PREVIEW / General Availability stage? |
@Ashish7812 all controllers regardless of their stage they get frequent patches (runtime fixes, CVE mitigations, image upgrade etc...)
Correct. |
@Ashish7812 The difference between GA and preview stage is that GA controllers get battle tested for around a week, are proven to be bug-free, and have stable performance on the long run. |
I am experimenting with the aws controller for k8. I am curious to know, how frequently the controllers adapt to the new features released by the corresponding services.
ex: if today a new feature is released for S3 does the same feature come with the controller also or there is a lag in adapting the new feature change into the controller?
The text was updated successfully, but these errors were encountered: