-
Notifications
You must be signed in to change notification settings - Fork 14
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
Modifications to Run integration Tests With Sail Operator #300
Modifications to Run integration Tests With Sail Operator #300
Conversation
prow/integ-suite-ocp.sh
Outdated
@@ -135,6 +135,13 @@ base_cmd=("go" "test" "-p" "1" "-v" "-count=1" "-tags=integ" "-vet=off" "-timeou | |||
"--istio.test.tag=${TAG}" | |||
"--istio.test.openshift") | |||
|
|||
# Append sail operator setup script to base command | |||
if [ "${OPERATOR_TYPE:-}" == "sail" ]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to initialize at the beginning of the file OPERATOR_TYPE
with some default value, but I don't like the name of the var. We are going to run the sail-operator-setup bash script to avoid doing some hacks or workaround when we want to run this integration test on OCP and against sail operator-based installed control plane, I think we can name this var something like CONTROL_PLANE_INSTALLER
(The same as the istio flag) and the default value should be istio
. And you can add here also some notes to explain the flags
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, Check the script we will need later to delete SKIP_TEST_RUN
because it is not going to be used anymore, but this can be done after the merge of the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to initialize at the beginning of the file
OPERATOR_TYPE
with some default value, but I don't like the name of the var. We are going to run the sail-operator-setup bash script to avoid doing some hacks or workaround when we want to run this integration test on OCP and against sail operator-based installed control plane, I think we can name this var something likeCONTROL_PLANE_INSTALLER
(The same as the istio flag) and the default value should beistio
. And you can add here also some notes to explain the flags
CONTROL_PLANE_INSTALLER is referring to this file in istio flag. So it might be confusing to use it for something else. I can change it to CONTROL_PLANE_TYPE and default it to istio on top of the script. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it can be CONTROL_PLANE_SOURCE
? And the values can be sail or istio
@@ -0,0 +1,8 @@ | |||
apiVersion: sailoperator.io/v1alpha1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe rename this file to istio-cni.yaml
only
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this :), I leave some comments mostly for clarity. Please tell me and I can add a new job to start running test over this new way to execute the test
prow/setup/sail-operator-setup.sh
Outdated
WORKDIR="$2" | ||
IOP_FILE="$2"/iop.yaml | ||
SAIL_IOP_FILE="$(basename "${IOP_FILE%.yaml}")-sail.yaml" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add note to explain what is the iop file
prow/setup/sail-operator-setup.sh
Outdated
IOP_FILE="$2"/iop.yaml | ||
SAIL_IOP_FILE="$(basename "${IOP_FILE%.yaml}")-sail.yaml" | ||
|
||
ISTIO_VERSION="${ISTIO_VERSION:-v1.24.1}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current Istio version is 1.24.2; is there any chance to fill this by default? I don't know if it is possible to be honest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One option is to use "latest" as istio version, I am not sure if it works for istio-cni but works for istiod. If you think its better idea I can modify default to latest and test it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, try this
prow/setup/sail-operator-setup.sh
Outdated
INGRESS_GATEWAY_SVC_NAMESPACE="${INGRESS_GATEWAY_SVC_NAMESPACE:-istio-system}" | ||
ISTIOCNI_NAMESPACE="${ISTIOCNI_NAMESPACE:-istio-cni}" | ||
|
||
ISTIOCNI="${PROW}/config/sail-operator/istioCNI-cr.yaml" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you change the name of the file, this will need to change also
/test istio-integration-telemetry |
/retest |
/test istio-telemetry-sail-controlpane |
@ctartici: The specified target(s) for
The following commands are available to trigger optional jobs:
Use In response to this:
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. |
/retest |
Important: Adding do not merge label until |
c2ab34c
to
44ff87d
Compare
@ctartici: The specified target(s) for
The following commands are available to trigger optional jobs:
Use In response to this:
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. |
/test istio-telemetry-sail-controlplane |
metadata: | ||
name: default | ||
spec: | ||
namespace: ${ISTIOCNI_NAESPACE} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo:
namespace: ${ISTIOCNI_NAESPACE} | |
namespace: ${ISTIOCNI_NAMESPACE} |
f9ef06b
to
e16e671
Compare
/test istio-telemetry-sail-controlplane |
/test istio-telemetry-sail-controlplane |
1 similar comment
/test istio-telemetry-sail-controlplane |
/test istio-telemetry-sail-controlplane |
spec: | ||
namespace: ${ISTIOCNI_NAMESPACE} | ||
version: ${ISTIO_VERSION} | ||
profile: openshift |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: is a profile needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure about this. Got the yaml from our jenkins config files. I can remove and test it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's test in a consecutive PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm in general I just leave some minor comments
If is ready, you can set the PR to ready to review to execute the prow jobs |
prow/setup/sail-operator-setup.sh
Outdated
IOP_FILE="$2"/iop.yaml | ||
SAIL_IOP_FILE="$(basename "${IOP_FILE%.yaml}")-sail.yaml" | ||
|
||
ISTIO_VERSION="${ISTIO_VERSION:-v1.24-latest}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the current master branch of Istio is 1.25 but we do not support it officially, in our main branch we can deploy master. Maybe worth checking if we can set an alias here to deploy by default the master alias
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is this file stating version: https://github.com/ctartici/istio_ossm/blob/master/VERSION but it has 1.26 for now. Where should I read the version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can use this one I guess, WDYT? https://github.com/ctartici/sail-operator/blob/main/pkg/istioversion/versions.yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, using the versions.yaml file will be the best I think
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one more comment related to the Istio resource version
/test istio-integration-telemetry |
@ctartici: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
/test istio-integration-helm |
# get istio version from versions.yaml | ||
VERSION_FILE="https://raw.githubusercontent.com/istio-ecosystem/sail-operator/$CONVERTER_BRANCH/pkg/istioversion/versions.yaml" | ||
if [ -z "${ISTIO_VERSION:-}" ]; then | ||
ISTIO_VERSION="$(curl -s "$VERSION_FILE" | grep -E 'name: v[0-9]+\.[0-9]+' | sed -E 's/.*(v[0-9]+\.[0-9]+).*/\1/' | sort -Vr | head -n1)-latest" | ||
fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very small change: I think it will be better to set also branch
alternative to be able to run in the master branch against the master of the versions.yaml
and we can set it later for another branch the same. It will be a small change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
really change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's merge this and start to make changes from there if they are needed
85e1ac5
into
openshift-service-mesh:master
Please provide a description of this PR:
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.
Please check any characteristics that apply to this pull request.