* Make it clearer in which cases you need to install an additional ingress controller and in which you don't
* Move Ingress Controller docs closer to the cluster provisioning docs
* Move hosted kubernetes cluster docs to k8s-tutorial so that they are next to the RKE, RKE2 and K3s docs in the menu
Fixes https://github.com/rancher/docs/issues/4109
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
Since 2.6 the tenant id is automatically looked up by rancher and can't be provided by the UI anymore.
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
This adds a detailed description on how to configure tls version and ciphers when Rancher is installed in a Kubernetes cluster. TLS is offloaded at the ingress controller, which means these settings need to be set there instead of the Rancher Pod/Container.
For running Rancher as a single Docker container, the default values have been updated to the ones currently supported.
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
This page was accidentally removed when the legacy catalogs and multi cluster app docs were removed in the 2.6 docs. The documentation on how to create these apps is still relevant in the 2.6 app marketplace though.
This re-adds this pages and updates it to the 2.6 copy and featureset.
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
This clarifies that there is no built-in integration at the moment, but that you can use Vault with its standard Kubernetes integration.
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
* Instead of duplication the traefik.yaml, the preferred way to customize Treafik is to use a HelmChartConfig manifest.
* The link to the Traefik was pointing to a deprecated and outdated repository.
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
The CN must be a hostname without a protocol.
With the protocol the command even fails because of the missing escaping of the forward slashes:
openssl req -x509 -newkey rsa:2048 -keyout myservice.key -out myservice.cert -days 365 -nodes -subj '/CN=https://myservice.example.com'
Generating a 2048 bit RSA private key
..+++
...........................+++
writing new private key to 'myservice.key'
-----
end of string encountered while processing type of subject name element #1
problems making Certificate Request
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
* Cluster Upgrades are possible for imported RKE2 clusters
* CIS Scans are available for all types of clusters in 2.5
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
Port requirements were documented in 3 places in the Rancher docs. This consolidates the documentation in one place and correctly distinguishes between the Rancher management cluster and downstream clusters.
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
* Add more default information how to remove monitoring v1
* Add documentation how to migrate a v1 alert through the new PrometheusRule UI
* Add a note how to migrate v1 notifiers
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
* Explain in text and with screenshots how to correctly configure the Rancher SAML client in Keycloak, including mappers
* Provide examples for field configurations in Rancher that map to the Keycloak defaults
* Move the note on how to get a metadata.xml file with Keycloak >= 6.0.0 directly to the Prerequisites so that it is hard to miss
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
This prevents the table to automatically be included on pages of other bundles.
By including the page instead of reading the file also the shortcodes in the table are expanded correctly.
This fixes broken links in the table.
Fixes https://github.com/rancher/docs/issues/2577
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
This prevents the table to automatically be included on pages of other bundles.
By including the page instead of reading the file also the shortcodes in the table are expanded correctly.
This fixes broken links in the table.
Fixes https://github.com/rancher/docs/issues/2577
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
Currently there are 4 different occurrences of the cluster capabilities table that compares which features you can use in Rancher with RKE clusters, hosted cloud provider clusters and imported clusters. One of them is very detailed but a bit outdated, the other ones only mention basic features and are not complete.
This commit centralizes the table and includes it on all 4 pages and updates it for features introduced with 2.4
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
This hardcodes the generated key name in all `kubectl create secret` commands where the `--from-file` option is used. It ensures that the stored key is the one that Rancher expects and does not rely on the local file name.
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
This prevents the table to automatically be included on pages of other bundles.
By including the page instead of reading the file also the shortcodes in the table are expanded correctly.
This fixes broken links in the table.
Fixes https://github.com/rancher/docs/issues/2577
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
This prevents the table to automatically be included on pages of other bundles.
By including the page instead of reading the file also the shortcodes in the table are expanded correctly.
This fixes broken links in the table.
Fixes https://github.com/rancher/docs/issues/2577
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
Currently there are 4 different occurrences of the cluster capabilities table that compares which features you can use in Rancher with RKE clusters, hosted cloud provider clusters and imported clusters. One of them is very detailed but a bit outdated, the other ones only mention basic features and are not complete.
This commit centralizes the table and includes it on all 4 pages and updates it for features introduced with 2.4
Signed-off-by: Bastian Hofmann <bashofmann@gmail.com>
Bastian Hofmann
