Skip to content
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

[BUG] Respositories reach behind a Proxy #45417

Open
frit0-rb opened this issue May 8, 2024 · 0 comments
Open

[BUG] Respositories reach behind a Proxy #45417

frit0-rb opened this issue May 8, 2024 · 0 comments
Labels
kind/bug Issues that are defects reported by users or that we know have reached a real release

Comments

@frit0-rb
Copy link

frit0-rb commented May 8, 2024

Rancher Server Setup

  • Rancher version: 2.8.3
  • Installation option (Docker install/Helm Chart): Helm Chart
    • If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):
  • Proxy/Cert Details:

Information about the Cluster

  • Kubernetes version: 1.26.15
  • Cluster Type (Local/Downstream): Downstream
    • If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): Imported

User Information

  • What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)
    • If custom, define the set of permissions: Admin

Describe the bug

I update Rancher from 2.7.10 to 2.8.3 and in that moment my Cluster imported lost communication with Rancher repositories

To Reproduce

Result

Expected Result

Screenshots

image

Additional context

I got a proxi working in our red, but the proxie setting is added correctly in /etc/rancher/rke2/.

More info. In the local cluster the apps and repositories reach them with out any problem

@frit0-rb frit0-rb added the kind/bug Issues that are defects reported by users or that we know have reached a real release label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues that are defects reported by users or that we know have reached a real release
Projects
None yet
Development

No branches or pull requests

1 participant