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

Add overrides testing in lifecycle integration tests #10752

Merged
merged 2 commits into from
Feb 11, 2021

Conversation

rifelpet
Copy link
Member

@rifelpet rifelpet commented Feb 7, 2021

This allows specific changes to be tested on an existing cluster during an update cluster --yes and ensuring a subsequent update cluster dryrun correctly reports no changes.

To specify changes, create a cluster.overrides.txt or instancegroup.<name>.overrides.txt file in the update_cluster integration test's directory as demonstrated here.

Each line is a field=value format, each batch of changes is separated by a --- line.
Each batch will be ran through update cluster --yes on its own.

In particular, reverting #10742 correctly caused a panic, so these tests are now capable of exposing those types of bugs.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 7, 2021
@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 Feb 7, 2021
This allows specific changes to be tested during an `update cluster --yes` and ensuring a subsequent `update cluster` dryrun correctly reports no changes.

To specify changes, create a cluster.overrides.txt or instancegroup.<name>.overrides.txt file in the update_cluster integration test's directory.
Each line is a field=value format, each batch of changes is separated by a `---` line.
Each batch will be ran through `update cluster --yes`
@rifelpet rifelpet force-pushed the lifecycle-integration-test branch from f153d2d to dd1ebb8 Compare February 7, 2021 05:18
@rifelpet
Copy link
Member Author

rifelpet commented Feb 7, 2021

/test pull-kops-e2e-k8s-containerd

@rifelpet
Copy link
Member Author

/test pull-kops-e2e-kubernetes-aws

@hakman
Copy link
Member

hakman commented Feb 11, 2021

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 11, 2021
@k8s-ci-robot k8s-ci-robot merged commit 63baa5b into kubernetes:master Feb 11, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.20 milestone Feb 11, 2021
@rifelpet rifelpet deleted the lifecycle-integration-test branch May 5, 2021 13:45
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. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants