-
Notifications
You must be signed in to change notification settings - Fork 33
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
Support for OSSM v2.6 #857
Conversation
c0c5f9a
to
3b5aa27
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #857 +/- ##
==========================================
- Coverage 80.20% 78.67% -1.54%
==========================================
Files 64 91 +27
Lines 4492 7066 +2574
==========================================
+ Hits 3603 5559 +1956
- Misses 600 1092 +492
- Partials 289 415 +126
Flags with carried forward coverage won't be shown. Click here to find out more.
|
49c5b23
to
f1939eb
Compare
Signed-off-by: Adam Cattermole <acatterm@redhat.com>
Signed-off-by: Adam Cattermole <acatterm@redhat.com>
Signed-off-by: Adam Cattermole <acatterm@redhat.com>
2471b2f
to
aec0c22
Compare
@adam-cattermole in the verification we use the existing ingress pod? Do you know if it is possible to set up a new Gateway using Gateway API in another ns for example? |
@maleck13 I didn't test that gateway with kuadrant, but did try deploying a gateway in a diff ns using gateway API successfully |
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.
changes look fine to me. I am upgrading my OCP cluster to give the verification a try.
@adam-cattermole @trepel @jsmolar Note I tested this on my hosted OCP cluster using 4.16.x I followed @adam-cattermole guide but instead of using the internal service name as the address I allowed an AWS LB to be spun up to expose the gateway externally.
After that everything worked. I tested DNSPolicy in this context also |
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.
verfied all works with 2.6 slightly modified instructions to allow external traffic
@adam-cattermole we should probably have an issue for documenting setting up Kuadrant with OSSM 2.6 as a follow on
Changes
Updates to support OSSM v2.6, primarily due to changes in types
Verification
Verified on OpenShift v4.16 - Steps adapted from existing guide
CLUSTER_DOMAIN
to the domain of your cluster as follows:kubectl cluster-info https://api.$CLUSTER_DOMAIN:6443
Install OSSM v2.6.1 through the OperatorHub
Create a namespace for istio
ServiceMeshControlPlane
inClusterWide
modeGateway
it is for:toystore
namespace as aServiceMeshMember
oc expose -n istio-system service/istio-ingressgateway --port 8080 --name toystore --hostname=api.toystore.apps.$CLUSTER_DOMAIN