-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Validate Rancher HA installs on k3s clusters. #25495
Comments
According to our staging documentation, https://staging.rancher.com/docs/rancher/v2.x/en/installation/k8s-install/kubernetes-rke/, we start K3s without deploying
|
Verified with Rancher server
Set LB and route 53
Existing automation passes on a 3 node custom cluster, all roles. |
k3s HA install has been validated using mysql and postgresql for AWS datastores. |
HA install validated for k3s version kubectl and exec shell work in the following browsers: Previous issues prevent Traefik from being the recommended ingress controller over nginx: |
run K3s I can exec shell and view logs in both the local cluster and clusters provisioned by Rancher in Rancher UI and using the kubeconfig file from Rancher UI. |
Waiting on new K3s release with nginx as default provider for Ingress - k3s-io/k3s#817 |
HA install validated for k3s version kubectl and exec shell work in the following browsers: We will use Traefik as the default provider for ingress. Testing was done using |
Validate running Rancher in k3s HA setup in an air-gapped environment The setup:
Add a custom cluster into Rancher:
The following checks are done:
|
No description provided.
The text was updated successfully, but these errors were encountered: