-
Notifications
You must be signed in to change notification settings - Fork 252
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
chore: improve the operator deployment detection #4427
Conversation
❗ By default, the pull request is configured to backport to all release branches.
|
b3aa47d
to
0571a48
Compare
/test feature_type=operator test_level=4 |
@jsilvela, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/8985522953 |
/test feature_type=operator test_level=4 |
@jsilvela, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/8987412660 |
@jsilvela, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/8987414033 |
/test feature_type=operator test_level=4 limit=local depoth=schedule |
@sxd, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/9098443345 |
/test feature_type=operator test_level=4 limit=local depoth=schedule |
@sxd, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/9098860101 |
Using the Deployment object from the Kubernetes environment we can get all the information for the deployment more accurated than just listing and couting pods, which it's an issue when you have another pod in the same namespace. Closes #4426 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com> Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com> Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com> Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
This patch makes the E2e tests get the number of operator Pods by looking into the Deployment resource instead of counting the listed Pods. The E2e tests will now work when more than one operator is deployed in the same namespace, i.e. when operators are deployed with OLM. Closes #4426 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com> Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com> Co-authored-by: Jaime Silvela <jaime.silvela@enterprisedb.com> (cherry picked from commit 32528f4)
This patch makes the E2e tests get the number of operator Pods by looking into the Deployment resource instead of counting the listed Pods. The E2e tests will now work when more than one operator is deployed in the same namespace, i.e. when operators are deployed with OLM. Closes #4426 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com> Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com> Co-authored-by: Jaime Silvela <jaime.silvela@enterprisedb.com> (cherry picked from commit 32528f4)
This patch makes the E2e tests get the number of operator Pods by looking into the Deployment resource instead of counting the listed Pods. The E2e tests will now work when more than one operator is deployed in the same namespace, i.e. when operators are deployed with OLM. Closes #4426 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com> Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com> Co-authored-by: Jaime Silvela <jaime.silvela@enterprisedb.com> (cherry picked from commit 32528f4)
Using the Deployment object from the Kubernetes environment we can get all the information for the deployment more accurate than just listing and counting pods, which it's an issue when you have another pod in the same namespace.
Closes #4426