https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# kubernetes
a
This message was deleted.
c
Have you opened a support ticket yet?
c
c
I meant like, an actual ticket for support. We sometimes get folks coming on here with paid support contracts and production outages that haven't created a ticket yet. Community Slack support is best-effort and folks on here are mostly devs or other free users so you're not likely to get a ton of handholding.
c
You mean I am on my own without paid support contract?
c
If you have specific questions they are more likely to get answers. We're not a VC funded startup burning cash for fun, if we gave everyone hands-on production SLAd support for free there would be no money to pay anyone with and there wouldn't be a product at all.
Open source is free as in beer, so the saying goes.
If you can diagnose it to a specific problem with the project it's highly likely to get fixed. Hands-on troubleshooting isn't something we can offer gratis.
c
I understand that you have to make money, esp. after the expensive acquisition.
I had the impression that I am not the only one with this problem. I can help to examine the problem for the benefit of all, including Suse's paying customers. Its a give and take, as for other Open Source projects. IMHO.
c
I see there was some back and forth on the ticket, with another community user, but it looks like you weren't interested in doing additional troubleshooting on a production system, which is understandable. Hard to say specifically what's going from the info that's in the ticket there.
Will probably require digging around in various pod logs and checking component versions. Older versions of cert-manager in particular aren't compatible with 1.22. cert-manager is a rancher dependency, and as far as I know is not managed by either rancher or rke when you upgrade versions.
c
When I started with Rancher cert-manager was not a dependency. It was sufficient to create a secret holding a Digicert certificate to hand-off on the helm install command line. See the 3rd option on https://rancher.com/docs/rancher/v2.5/en/installation/install-rancher-on-k8s/#3-choose-your-ssl-configuration. I would guess that if cert-manager is a problem here, then its because it is not installed. Right now I am setting up a second cluster to verify Rancher's migration procedure. Using a different host name for the cluster this won't affect my production environment (hopefully).
PS: Bad link, but the current documentation for 2.6 appears to be the same wrt cert-manager.
Hi @creamy-pencil-82913, can you confirm that cert-manager is not a dependency, or is the documentation misleading? I managed to upgrade my rke cluster running Rancher to v1.21.12-rancher1-1 and Rancher version 2.6.5. Seems to be working fine. If I try to upgrade rke to version v1.23.6-rancher1-1 then Rancher becomes unresponsive, as for version 1.22.x before. The managed clusters cannot be accessed via kubectl anymore (which is unacceptable). The web browser cannot connect to the front-end, either.
FYI: Using the stage system I guess I found out what the problem is: apparmor. For the old kubernetes v1.21 this wasn't a problem, but using v1.22 + it is. After dropping apparmor the web interface is available again. To be sure I have to upgrade my production system, of course.
10 Views
Open in Slack
PreviousNext
Powered by