How frequently the controllers are patched with new fetures released by the respective services?
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?
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?
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 What is the plan to make it to GA?
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?
When you say the controllers are patched immediately, do you mean for services that are already in the General Availability stage?
@Ashish7812 all controllers regardless of their stage they get frequent patches (runtime fixes, CVE mitigations, image upgrade etc...)
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?
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.
Issues go stale after 180d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 60d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale
Stale issues rot after 60d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 60d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle rotten
Rotten issues close after 60d of inactivity.
Reopen the issue with /reopen.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/close
@ack-bot: Closing this issue.
In response to this:
Rotten issues close after 60d of inactivity. Reopen the issue with
/reopen. Provide feedback via https://github.com/aws-controllers-k8s/community. /close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.