Skip to content
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

[Feature Request] KaaS conformance tests with other providers/implementations #649

Open
martinmo opened this issue Jun 26, 2024 · 5 comments
Assignees
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling enhancement New feature or request SCS is continuously built and tested SCS is continuously built and tested in order to raise velocity and quality SCS is standardized SCS is standardized SCS-VP10 Related to tender lot SCS-VP10

Comments

@martinmo
Copy link
Member

At the moment, conformance tests run as part of our Zuul E2E tests and only for the reference implementation. Other implementations and clouds should be included, e.g., Gardener on REGIO.cloud.

CC @tonifinger

@martinmo martinmo added enhancement New feature or request Container Issues or pull requests relevant for Team 2: Container Infra and Tooling SCS is continuously built and tested SCS is continuously built and tested in order to raise velocity and quality SCS is standardized SCS is standardized SCS-VP10 Related to tender lot SCS-VP10 labels Jun 26, 2024
@martinmo martinmo self-assigned this Jun 26, 2024
@martinmo martinmo mentioned this issue Jun 26, 2024
29 tasks
@mbuechse
Copy link
Contributor

@mxmxchere Can you provide us with a cluster or two? Ideally, one for each active k8s branch, but if we could use some kind of self-service (API) to create and tear down clusters ad-hoc for our conformance tests, that would be even better.

@mxmxchere
Copy link
Contributor

Sounds like a perfect use case for the moin-cluster. The cluster comes pre-deployed with a few (currently one, planned are more) clusterstacks. You can login via oidc. Some namespaces are pre-equipped with credentials for gx-scs. You can find infos here. To access the predeployed namespaces you have to be member of the team moin-cluster-all-playgrounds. Btw @jschoone will host a little intro presentation on how to use the cluster in tomorrows community-call. A bulk-PR to add people to the all-playgrounds-team is also planned.

@martinmo
Copy link
Member Author

@mxmxchere I am already part of the moin-cluster-playground1 team, but with the kubeconfig described in the usage I can't list the pods:

$ kubectl get pods
Error from server (Forbidden): pods is forbidden: User "oidc:martinmo" cannot list resource "pods" in API group "" in the namespace "default"

I also tried namespaces playground1 and kaas-playground1 with the same result. OIDC login via GitHub worked as expected, however.

@martinmo
Copy link
Member Author

martinmo commented Jun 27, 2024

Infos from today's Container Call:

Currently, there is some restructuring going on in the Moin cluster and the moin-cluster-playground1 team has no access anymore. Instead, it is planned to create the team as outlined above. This will be announced in a lightning talk today.

For getting access to Gardener based clusters we can use Plusserver PSKE or regiocloud. Credentials can be obtained from @joshmue and @mxmxchere, respectively.

@mbuechse
Copy link
Contributor

Yes, please! Go ahead.

@anjastrunk anjastrunk moved this from Backlog to Doing in Sovereign Cloud Stack Sep 4, 2024
@martinmo martinmo removed their assignment Sep 5, 2024
@tonifinger tonifinger self-assigned this Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling enhancement New feature or request SCS is continuously built and tested SCS is continuously built and tested in order to raise velocity and quality SCS is standardized SCS is standardized SCS-VP10 Related to tender lot SCS-VP10
Projects
Status: Doing
Development

No branches or pull requests

5 participants