Azure / Azure/OpenShift

Accessing Cluster Console with Private Cluster is not working and DNS uses public ip instead of private.

Open
#134 1 comment 0 reactions 1 assignee Claimed by @kwoodson View on GitHub
bug
Dominant language
No language data
Stars
121
Forks
42
PR merge metrics
No merged PRs in 30d

Description

If you deploy a private cluster as per the documentation

[https://github.com/Azure/OpenShift/blob/master/private-preview-docs/private-cluster.md](https://github.com/Azure/OpenShift/blob/master/private-preview-docs/private-cluster.md)

you'd have two different but perhaps related issues.

1. whenever you want to access Cluster Console via the web it gets you back to the catalog.

2. before it sends you back to the catalog it tries to open the URL console.apps.xxxxxxxx.location.azmosa.io which points to the public lb-api IP assigned and is not accessible in the Private deployment. This creates an authentication issue that takes you out from the web console. A workaround is to edit the hosts file and assign the private ip to the console fqdn. After doing that you can navigate normally through the console but have the issue 1 (no Cluster Console access)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.