Skip to content
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

tests: use reconcile command for kOps 1.31+ #17152

Merged

Conversation

justinsb
Copy link
Member

We expect people to start using the reconcile command
particularly for upgrades.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Dec 27, 2024
"${KOPS_B}" update cluster --admin --yes
# Verify no additional changes
"${KOPS_B}" update cluster
if [[ "${KOPS_VERSION_B}" =~ 1.3[123456789] ]]; then
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we should invert this, using the old method when the version matches 1.2 or 1.30. That way we avoid surprises when 1.40 is tested.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea 👍

@hakman
Copy link
Member

hakman commented Dec 28, 2024

/retest

@stl-victor-sudakov
Copy link

Are there any plans to document the reconcile command better and in more detail? As a kOps user, I do not quite understand the relation of this command especially to the "upgrade cluster" command.

As far as I understand, it does something like "if a rolling-update is required after an update, perform a rolling update now", is this right? But when do you run the single "kops reconcile cluster" command instead of "kops update cluster --reconcile" ?

@rifelpet rifelpet added this to the v1.31 milestone Jan 9, 2025
@hakman
Copy link
Member

hakman commented Jan 10, 2025

/test pull-kops-e2e-aws-upgrade-k130-ko130-to-klatest-kolatest-many-addons

"${KOPS_B}" update cluster
if [[ "${KOPS_VERSION_B}" =~ 1.3[123456789] ]]; then
# Preview changes
"${KOPS_B}" update cluster
Copy link
Member

@hakman hakman Jan 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Would be nice if kops reconcile cluster would show the same output as kops update cluster.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We've done this now, so switched to use reconcile cluster here

@hakman
Copy link
Member

hakman commented Jan 10, 2025

/override pull-kops-e2e-cni-flannel

@k8s-ci-robot
Copy link
Contributor

@hakman: Overrode contexts on behalf of hakman: pull-kops-e2e-cni-flannel

In response to this:

/override pull-kops-e2e-cni-flannel

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-sigs/prow repository.

We expect people to start using the reconcile command
particularly for upgrades.
@justinsb justinsb force-pushed the upgrade_tests_should_test_reconcile branch from 1e03e50 to d02ba27 Compare January 19, 2025 14:32
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 19, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rifelpet

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 19, 2025
@hakman
Copy link
Member

hakman commented Jan 19, 2025

/lgtm

@justinsb
Copy link
Member Author

/retest

1 similar comment
@hakman
Copy link
Member

hakman commented Jan 19, 2025

/retest

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Jan 19, 2025

@justinsb: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-kops-e2e-gce-cni-calico 1e03e50 link true /test pull-kops-e2e-gce-cni-calico
pull-kops-e2e-gce-cni-kindnet 1e03e50 link true /test pull-kops-e2e-gce-cni-kindnet
pull-kops-kubernetes-e2e-ubuntu-gce-build d02ba27 link false /test pull-kops-kubernetes-e2e-ubuntu-gce-build

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-sigs/prow repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot merged commit d04dad2 into kubernetes:master Jan 19, 2025
23 of 24 checks passed
@k8s-ci-robot k8s-ci-robot modified the milestones: v1.31, v1.32 Jan 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/office-hours lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants