Adding Solo.io to the Partners

[PetrMc]

Description of changes:

This pull request integrates Solo.io into the AWS EKS Anywhere Partners testing framework. It includes the following artifacts:

• FluxCD configuration
• Testing Job

These additions ensure that Solo.io's components are validated according to the AWS EKS Anywhere Partners' testing protocols.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[PetrMc]

@elamaran11 @shapirov103 - would appreciate your review and hopefully approval! Thanks!

[elamaran11]

@PetrMc Thankyou for the PR. Have some comments on the PR.

[elamaran11]

@PetrMc Please read requirement number 3. Please rework on the functional test job pls.

Healthchecks, service endpoints checks or any other technical checks do not represent sufficient coverage required for the functional test

[elamaran11]

@PetrMc Looks good at the moment. Our team will validate and get back in our EKS-A environments.

[elamaran11]

@mikemcd3912 Please validate in our lab.

[mikemcd3912]

Hi @PetrMc,

After validating in our baremetal lab I noted that the testjob script is set up to only run once, so we would like to see that updated to a Cronjob so that it can test at least daily. See Komodor or Kong for examples of this

In addition to the recurring job runs, we encountered an issue with the cleanup stage on that pod. solo-istiod-healthtest pod log output is as follows:

$ kubectl logs -n istio-system solo-istiod-healthtest-c46qx ─╯
Deploying custom Istio Ingress Gateway...
deployment.apps/custom-ingressgateway created
NAME READY UP-TO-DATE AVAILABLE AGE
custom-ingressgateway 0/1 1 0 0s
Waiting for the custom ingress gateway deployment to be ready...
Waiting for deployment "custom-ingressgateway" rollout to finish: 0 of 1 updated replicas are available...
deployment "custom-ingressgateway" successfully rolled out
Deploying test gateway...
gateway.networking.istio.io/httpbin-gateway created
NAME AGE
httpbin-gateway 0s
Deploying test VirtualService...
virtualservice.networking.istio.io/httpbin-virtualservice created
NAME GATEWAYS HOSTS AGE
httpbin-virtualservice ["httpbin-gateway"] ["httpbin.example.com"] 0s
Checking Istio Ingress Gateway configuration...
"name": "httpbin.example.com:80",
"httpbin.example.com"
Istio Ingress Gateway has received correct configuration from Istiod.
Cleaning up test resources...
virtualservice.networking.istio.io "httpbin-virtualservice" deleted
gateway.networking.istio.io "httpbin-gateway" deleted
Istio functional test completed successfully.
Cleaning up resources...
Error from server (NotFound): gateways.networking.istio.io "httpbin-gateway" not found
deployment.apps "custom-ingressgateway" deleted
Cleanup completed.

[PetrMc]

Thanks @mikemcd3912

• Good catch on cleaning up script - it's now adjusted - thanks.
• Job has been converted to CronJob (per @elamaran11 directions we did follow the requirements that are specifically state in CronJob to check status on all EKSA Resources #5 "Functional test must be implemented as a Kubernetes Job" - you might want to adjust the docs.

Hopefully the new commit addresses all the concerns. Thank you!

[mikemcd3912]

@PetrMc Thank you for the quick adjustment, and I appreciate the feedback on the docs! I can see how that current wording would be a bit unclear so we'll work to update that going forward

@elamaran11

• vmware testing successful, no issues noted with addon deployment or test job after the cleanup script adjustment
• baremetal testing reperformed successfully, no issues noted with addon deployment or test job after the cleanup script adjustment
• local testing successful, no issues noted with addon deployment or test job after the cleanup script adjustment

[elamaran11]

@PetrMc Thankyou for working with us on the Conformitron program to validate solo.io.
@mikemcd3912 Thankyou for validating in our labs. LGTM to merge.