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

[OK TO MERGE NOW] Prepare for next version #302

Merged
merged 2 commits into from
Dec 2, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Dec 2, 2024

DO NOT MERGE YET! The smoke test failed. Please fix the problem before merging this PR which updates version numbers and prepares for release v2.3.0

@jmazzitelli
Copy link
Contributor

This is OK to merge now... I ran the smoke tests on my local machine and all pass:

$ hack/smoke-test-release-branch.sh --release-branch helm-charts-release-162-main
[HACK] ===SETTINGS===
CLIENT_EXE=/home/jmazzite/bin/kubectl
GIT_LOCAL_DIR=/home/jmazzite/source/kiali/helm-charts/hack/..
GIT_REMOTE_NAME=origin
HELM_EXE=/home/jmazzite/bin/helm
KIND_EXE=/home/jmazzite/bin/kind
RELEASE_BRANCH=helm-charts-release-162-main
RELEASE_BRANCH_PATTERN=helm-charts-release-*
[HACK] Working in directory: /home/jmazzite/source/kiali/helm-charts
[HACK] Fetching latest content from git remote [origin]
X11 forwarding request failed on channel 0
[HACK] Will smoke test remote release branch [origin/helm-charts-release-162-main]
branch 'smoketest' set up to track 'origin/helm-charts-release-162-main' by rebasing.
Switched to a new branch 'smoketest'
NAME: kiali-operator
LAST DEPLOYED: Mon Dec  2 08:23:42 2024
NAMESPACE: smoketest-kiali-operator
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Welcome to Kiali! For more details on Kiali, see: https://kiali.io

The Kiali Operator [v2.2.0] has been installed in namespace [smoketest-kiali-operator]. It will be ready soon.
You have elected not to install a Kiali CR. You must first install a Kiali CR before you can access Kiali. The operator is watching all namespaces, so you can create the Kiali CR anywhere.

If you ever want to uninstall the Kiali Operator, remember to delete the Kiali CR first before uninstalling the operator to give the operator a chance to uninstall and remove all the Kiali Server resources.

(Helm: Chart=[kiali-operator], Release=[kiali-operator], Version=[2.2.0])
deployment.apps/kiali-operator condition met
pod/kiali-operator-6459ddfbb8-pxn8l condition met
release "kiali-operator" uninstalled
NAME: kiali-server
LAST DEPLOYED: Mon Dec  2 08:24:33 2024
NAMESPACE: smoketest-kiali-server
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Welcome to Kiali! For more details on Kiali, see: https://kiali.io

The Kiali Server [v2.2.0] has been installed in namespace [smoketest-kiali-server]. It will be ready soon.

When installing with "deployment.cluster_wide_access=false" using this Kiali Server Helm Chart,
it is your responsibility to manually create the proper Roles and RoleBindings for the Kiali Server
to have the correct permissions to access the service mesh namespaces.

(Helm: Chart=[kiali-server], Release=[kiali-server], Version=[2.2.0])
deployment.apps/kiali condition met
pod/kiali-864bc865f5-5gmbp condition met
release "kiali-server" uninstalled
[HACK] =========================
[HACK] The smoke test has PASSED
[HACK] =========================
[HACK] Restoring original git branch
Switched to branch 'master'
Your branch is up to date with 'origin/master'.
[HACK] Deleting the operator namespace used for the test
namespace "smoketest-kiali-operator" deleted
[HACK] Deleting the server namespace used for the test
namespace "smoketest-kiali-server" deleted

@jmazzitelli jmazzitelli changed the title [DO NOT MERGE YET] Prepare for next version [OK TO MERGE NOW] Prepare for next version Dec 2, 2024
@jmazzitelli jmazzitelli self-requested a review December 2, 2024 13:26
@leandroberetta leandroberetta merged commit 500f239 into master Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants