-
Notifications
You must be signed in to change notification settings - Fork 514
[hack-scripts][test] Support customized istio control plane namespace #7951
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
Comments
@mkralik3 , which hack scripts need to be updated? And which test files? Is this something you'd like to do, otherwise it would be great to have a more specific list, thanks. |
For the hack scripts, I haven't tried yet whether I can install bookinfo, e.g. to a different namespace (e.g. bookinfo2) and can it into the control-plane which is e.g. in Right now, I want to align downstream pipeline in Jenkins with upstream CI. That is why I am using |
@jmazzitelli , do you know if any of the relevant scripts support this already? |
@jshaughn |
Describe the bug
Hack scripts and tests assume that istio control plane is installed in the
istio-system
namespace (istio-system is hardcoded on more places in the test suites). Testing OSSM2 and OSSM3 together requires 2 control planes in two different namespaces against which the Kiali tests will run. ( to have it at least in the Kiali integration test and bookinfo install script)Add support for customization of control plane namespace to the hack script as well as tests.
(similar to #7950 but with more work to do)
Downstream issue: https://issues.redhat.com/browse/OSSM-8387
The text was updated successfully, but these errors were encountered: