-
Notifications
You must be signed in to change notification settings - Fork 21
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
[EPIC] Evaluate costs of making a cluster SCS compliant #426
Comments
I created a document to show what is necessary to make a Yaook cluster (OpenStack) compliant with SCS. It basically combines the standards into an easy to read document (and make it a bit easier). I'm not entirely sure where to post this document to keep the SCS-Team in the loop on this, but I think I will just create a branch that will never be merged. The most current version can always be found in our internal infrastructure, since the updates here will maybe be behind 1-2 days. Edit: https://github.com/SovereignCloudStack/standards/compare/do-not-merge/scs-compliant-yaook contains the documents. |
This commit should NEVER be merged into the main branch, since its only here for tracking in the project. Signed-off-by: Hannes Baum <hannes.baum@cloudandheat.com>
Good idea. General outcomes on how to make arbitrary OpenStack/KaaS cluster SCS compliant, should be documented in the corresponding issue, as listed in this epic. Furthermore, we should write blog articles, whenever a topic is value-added for CSPs and SCS community. |
I started to setup an independent K8s cluster that will be used to test the K8s standards. The cluster is already up and running, next step is to apply the standards. |
I finally created the k8s cluster from Nonetheless, I could create a cluster and will check this now for conformance with the SCS standards, especially Further information can be found in the issues regarding this. |
Add and extend some implementation notes derived from the findings of #426. Signed-off-by: Hannes Baum <hannes.baum@cloudandheat.com>
Add and extend some implementation notes derived from the findings of #426. Signed-off-by: Hannes Baum <hannes.baum@cloudandheat.com>
Add and extend some implementation notes derived from the findings of #426. Signed-off-by: Hannes Baum <hannes.baum@cloudandheat.com>
Add and extend some implementation notes derived from the findings of #426. Signed-off-by: Hannes Baum <hannes.baum@cloudandheat.com>
Add and extend some implementation notes derived from the findings of #426. Signed-off-by: Hannes Baum <hannes.baum@cloudandheat.com>
* Extend implementation notes Add and extend some implementation notes derived from the findings of #426. Signed-off-by: Hannes Baum <hannes.baum@cloudandheat.com> * Review adjustments Adjustments made possible by the review from @mbuechse. Signed-off-by: Hannes Baum <hannes.baum@cloudandheat.com> * Apply suggestions from code review Co-authored-by: Matthias Büchse <matthias.buechse@cloudandheat.com> Signed-off-by: Martin Morgenstern <martin.morgenstern@cloudandheat.com> * Remove impl note which became redundant after merging main Signed-off-by: Martin Morgenstern <martin.morgenstern@cloudandheat.com> * Remove outdated, wrong file SCS-Spec.Images.yaml Signed-off-by: Matthias Büchse <matthias.buechse@cloudandheat.com> * Make implementation notes more concrete Signed-off-by: Matthias Büchse <matthias.buechse@cloudandheat.com> * Update Standards/scs-0210-w1-k8s-version-policy-implementation-testing.md Signed-off-by: Matthias Büchse <matthias.buechse@cloudandheat.com> * Appease markdown-lint Signed-off-by: Matthias Büchse <matthias.buechse@cloudandheat.com> --------- Signed-off-by: Hannes Baum <hannes.baum@cloudandheat.com> Signed-off-by: Martin Morgenstern <martin.morgenstern@cloudandheat.com> Signed-off-by: Matthias Büchse <matthias.buechse@cloudandheat.com> Co-authored-by: Martin Morgenstern <martin.morgenstern@cloudandheat.com> Co-authored-by: Matthias Büchse <matthias.buechse@cloudandheat.com>
Epic issue to evaluate costs to make existing, non-compliant OpenStack and K8S cluster SCS compliant. In doing so, we set up a non-compliant cluster with the open source life Lifecycle Management Tool for OpenStack and K8S Yaook.
This issue acts as epic.
General
IaaS
[Other] Adapt C&H test cluster to Decisions for the Volume Type Standard (scs-0111) #428KaaS
[Other] Adapt C&H test cluster to Requirements for container registry (scs-0212) #422[Other] Adapt C&H test cluster to Kubernetes Nodes Anti Affinity (scs-0213) #423[Other] Adapt C&H test cluster to Requirements for testing cluster-stacks (scs-0216) #425Extra
The text was updated successfully, but these errors were encountered: