doc-caasp
doc-caasp copied to clipboard
SUSE
SUSE Container as a Service Platform Documentation
6.8.1.2 Deploy ingress controller from helm chart: https://documentation.suse.com/suse-caasp/4.5/html/caasp-admin/_security.html#_deploy_ingress_controller_from_helm_chart If the config from the previous section is used - which sets replica count to 3 - then there should be four...
SUSE CaaSP 4.5.3 is already downloadable by customers, but there is no changelog anywhere.
3.1.2.2.3 Migration Procedure (Air gap): https://documentation.suse.com/suse-caasp/4.5/html/caasp-admin/_software_management.html#_migration_procedure_air_gap ---------------------- Install the plugin export HELM_LINTER_PLUGIN_NO_INSTALL_HOOK=true helm plugin install ./helm-2to3 --> can you change this to: export HELM_LINTER_PLUGIN_NO_INSTALL_HOOK=true helm3 plugin install ./helm-2to3
4 Cluster Updates: https://documentation.suse.com/suse-caasp/4.5/single-html/caasp-admin/#_cluster_updates My customer like to have a procedure that outline step to migrate when yu have a SUSE Manager server. Currently the information is scattered among different...
At the moment ETCD is using a server.crt which per default only has the IP address of the master node it is running on. In case we want to scrape...
It seems the current way of adjusting addons is not valid as skuba automatically creates a kustomized.yaml in a temporary folder? See https://bugzilla.suse.com/show_bug.cgi?id=1177803 We need this properly documented in 4.2.x...
3.1.2.3.2 Migration Procedure: https://documentation.suse.com/suse-caasp/4.5/single-html/caasp-admin/#_migration_procedure ------------------- 1. before starting - create a list of deployments and repos - "helm list" and "helm repo list" 2. sudo zypper remove helm2 -> this...
5.1 Migration to SUSE CaaS Platform 4.5: https://documentation.suse.com/suse-caasp/4.5/single-html/caasp-admin/#caasp-migration ---------------------- For me it is unclear if we just upgrade the OS on the admin machine and skuba does the "zypper migration"...