This repository was archived by the owner on Feb 6, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 56
[WIP] Istio: Adding Traffic Management tests #1334
Open
mmnelemane
wants to merge
2,110
commits into
SUSE:master
Choose a base branch
from
mmnelemane:istio-test
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Otherwise it might cut the build number off, which is what ensures it being uniqe. Also make the README match.
Set CI labels from PR labels
This ensure the resulting PATH is a maximum of 1+3+1+70+1+10=86 bytes long. When ssh-agend -a NAME is called with a NAME that is too long it fails with: unix_listener: path "/home/jenkins/workspace/caasp-jobs/v4/e2e/vmware/⌦ test_upgrade_plan_from_previous_with_upgraded_control_plane-daily/⌦ agent.sock" too long for Unix domain socket Fixes: SUSE/avant-garde#1596
change ssh_sock to use TERRAFORM_STACK_NAME
Reorganize jobs adding the version as a parameter to give room for future v5 jobs. Signed-off-by: Pablo Chacin <pchacin@suse.com>
CI: Reorganize jobs per caasp version
Set platform from PR labels * If PR specifies a ci-platform label, override the default test platform. * PR tests can run in any supported platoform. Add the configuration required by libvirt to the environment.
After job reorganization introduced in da18f4a the name of the conformance test is not the one expected, as the 'conformace' postfix should had been removed. Signed-off-by: Pablo Chacin <pchacin@suse.com>
Some PR require experimental features that require workers with configurations that may conflict with regular workers. Signed-off-by: Pablo Chacin <pchacin@suse.com>
fix suggestion for vspshere configuration (#1618) Signed-off-by: cclhsu <clark.hsu@suse.com>
* Refactor code-lint logic Include the code-lint logic into the pr-test pipeline to unify the processing of all tests into one pipeline. * CI: Remove redundant PR jobs Once the author validation and code lint logic has been refactored into the pr-test job, the corresponding jobs and jenkins pipelines are redundant.
Unlike other Terraform providers, we are using the user/password authentication in libvirt. This is not needed as the cloud-init step will eventually configure the keys correctly and Terraform will be able to ssh into the VM. Besides, it avoids a problem we are seeing between ssh-agent and terraform: hashicorp/terraform#23662 Signed-off-by: Manuel Buil <mbuil@suse.com>
Run daily jobs for multiple versions, each with a different source branch. Also select the worker type based on the branch. Signed-off-by: Pablo Chacin <pchacin@suse.com>
Use double quotes in worker label to allow for variable substitution. Signed-off-by: Pablo Chacin <pchacin@suse.com>
…titution Fix quotes in label to allow variable substitution
Signed-off-by: Vicente Zepeda Mas <vzepedamas@suse.com>
Signed-off-by: Vicente Zepeda Mas <vzepedamas@suse.com>
Signed-off-by: Vicente Zepeda Mas <vzepedamas@suse.com>
Signed-off-by: Vicente Zepeda Mas <vzepedamas@suse.com>
Signed-off-by: Vicente Zepeda Mas <vzepedamas@suse.com>
Kubernetes 1.17 requires go version 1.13[1]. This change updates the makefile version check and the package spec file template to require go 1.13 and updates the module list with `go mod tidy`. This change will require an update to the Jenkins workers to use 1.13. [1] https://kubernetes.io/docs/setup/release/notes/#dependencies
If ci-repo label is specified, set the BRANCH_REPO environment variable to add this repo branch to the cluster nodes. Signed-off-by: Pablo Chacin <pchacin@suse.com>
Separate jobs in different projects depending on the version of CaaSP to facilitate adapting their configuration independently. Signed-off-by: Pablo Chacin <pchacin@suse.com>
Following the convention that master and feature branches will use the default integration worker type, while the experimental-feature and maintenance-version branches will use the corresponding worker types. Signed-off-by: Pablo Chacin <pchacin@suse.com>
Make v4 run from maintenance-caasp-v4 and v5 from master Signed-off-by: Pablo Chacin <pchacin@suse.com>
…t-brach Select worker type based on target branch for PR
We'd like to test the v5 versions of the k8s images.
gangway image version was increased to 5 at this commit SUSE/caasp-container-images@0f9800c#diff-45f24944e51aad4524696dae7dc47b2e in order to fix bsc#1173165 Note this should be also backported to maintenance-caaspv4 Signed-off-by: Jordi Massaguer Pla <jmassaguerpla@suse.de>
Use checkout step for checking out and automatically merging the pr into the target branch. Signed-off-by: Pablo Chacin <pchacin@suse.com>
This implements a basic drain and uncordon before/after running `kubeadm upgrade`. To achieve that we also have to add a new helper function `kubernetes.UncordonNode()`. Signed-off-by: Sascha Grunert <sgrunert@suse.com>
Merge PR into target Branch before building
Drain nodes before kubadm upgrade and uncordon afterwards
fix gangway revision (bsc#1173165)
Remove test that is not part of the minimal functionality to be tested for approving a PR. Signed-off-by: Pablo Chacin <pchacin@suse.com>
…t-from-pr Remove addon upgrade test from pr pipeline
Updated versions to v4.5 includes packages and ci
updated version to v4.5
Revert k8s 1.17.9 upgrade
Signed-off-by: Manuel Buil <mbuil@suse.com>
Add the CA repo
47e72cc
to
ca4ab6e
Compare
is this still valid @mmnelemane? has networking reviewed it @mbologna ? It still needs an update...and it should be fast otherwise we should just close it. |
@Itxaka A simplified test was included in Skuba and since there was no plan to include Istio in the CaaSP release, I stopped this expansion. I think it can be closed for now unless someone still requests for Istio on CaaSP 4.5. |
I would let the branch stay, so that we can use it if needed in future. |
Thanks for the update @mmnelemane Closing the Pr does not remove the branch btw. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why is this PR needed?
Does it fix an issue? addresses a business case?
add a description and link to the issue if one exists.
Fixes #
Reminder: Add the "fixes bsc#XXXX" to the title of the commit so that it will
appear in the changelog.
What does this PR do?
please include a brief "management" technical overview (details are in the code)
Anything else a reviewer needs to know?
Special test cases, manual steps, links to resources or anything else that could be helpful to the reviewer.
Info for QA
This is info for QA so that they can validate this. This is mandatory if this PR fixes a bug.
If this is a new feature, a good description in "What does this PR do" may be enough.
Related info
Info that can be relevant for QA:
Status BEFORE applying the patch
How can we reproduce the issue? How can we see this issue? Please provide the steps and the prove
this issue is not fixed.
Status AFTER applying the patch
How can we validate this issue is fixed? Please provide the steps and the prove this issue is fixed.
Docs
If docs need to be updated, please add a link to a PR to https://github.com/SUSE/doc-caasp.
At the time of creating the issue, this PR can be work in progress (set its title to [WIP]),
but the documentation needs to be finalized before the PR can be merged.
Merge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises: