-
Notifications
You must be signed in to change notification settings - Fork 55
This series is a re-rewrite of the image generator code and related manifests #375
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
Conversation
a62a0d7
to
474b288
Compare
Catalog for testing: quay.io/bpradipt/openshift-sandboxed-containers-operator-catalog:v1.5.2 |
|
6fd6c68
to
da4a26e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
da4a26e
to
eb2913b
Compare
@snir911 catalog for testing - quay.io/bpradipt/openshift-sandboxed-containers-operator-catalog:v1.5.2 |
eb2913b
to
5c7e8eb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall, assuming pre-merge testing was ok, thanks!
22672be
to
f71d64f
Compare
new AMI generation flow was pre-merge tested |
29f36d8
to
f95c5c1
Compare
I appreciate Pradipta's effort to produce quality code, after few iterations we managed to:
status: |
c89e239
to
51994da
Compare
51994da
to
ce078f4
Compare
1. Fix reading of required attributes from secret and configmap 2. Refactor code for better readibility and modularity 3. Add event notification to indicate the status of the job 4. Improve job status evaluation 5. Convert image generator instance to singleton Signed-off-by: Pradipta Banerjee <[email protected]>
The event "reason" code is used as the cache key. The default time for suppressing the event having the same reason code is 2 min. Signed-off-by: Pradipta Banerjee <[email protected]>
Move the podvm image creation post kata installation. Otherwise the kata installation remains stuck with no indication on what is happening Signed-off-by: Pradipta Banerjee <[email protected]>
Signed-off-by: Pradipta Banerjee <[email protected]>
ce078f4
to
aad8918
Compare
@gkurz @pmores @littlejawa @jensfr if you have time, it will be great to have your comments on this PR, especially on the following:
The latest code is pre-merge tested by @vvoronko Thanks a lot for his help. |
There are cloud provider specific handler scripts for image creation and deletion. Also better error handling and documented scripts Signed-off-by: Pradipta Banerjee <[email protected]>
The controller-manager was gettign OOMkilled with latest changes. Hence bumping up the memory limit Signed-off-by: Pradipta Banerjee <[email protected]>
Consolidate all podvm image related constant in a single place Signed-off-by: Pradipta Banerjee <[email protected]>
This can be used in openshift controller for updating KataConfig CRD Status Signed-off-by: Pradipta Banerjee <[email protected]>
Add status update to KataConfig as well in addition to Kubernetes events Signed-off-by: Pradipta Banerjee <[email protected]>
Modify error strings to not use caps Signed-off-by: Pradipta Banerjee <[email protected]>
Adjust the return values to ensure error is the last return value. Also avoids go-staticcheck warnings Signed-off-by: Pradipta Banerjee <[email protected]>
getConditionReason and kataOcExists methods are no longer used. However let's keep it for now but ignore it as part of staticcheck warnings Signed-off-by: Pradipta Banerjee <[email protected]>
aad8918
to
fe0fdc0
Compare
If you meant whether this PR changes the AMI image that gets created using the existing code, then answer is yes. Since this will use latest pod vm components (like agent, protocol-forwarder etc) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @littlejawa @snir911 for acks |
/override ci/prow/check |
1 similar comment
/override ci/prow/check |
@bpradipt: Overrode contexts on behalf of bpradipt: ci/prow/check In response to this:
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. |
@gkurz: Overrode contexts on behalf of gkurz: ci/prow/check In response to this:
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. |
@bpradipt: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
Closes https://issues.redhat.com/browse/KATA-2633
Current flow : Create podvm image -> create mcp, kata rpm etc -> create kata runtimeclass -> create kata-remote runtimeclass
New flow: create mcp, kata rpm etc -> create kata runtimeclass -> create podvm image -> create kata-remote runtimeclass
The image generation status events are posted as Kubernetes events for monitoring
How to check for events during image generation when creating kataconfig?
How to check for events during image deletion when deleting kataconfig?