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.

Sign up for GitHub

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

Jump to bottom

Create an Ingress object for Metalk8s UI #1799

Closed
nootal opened this issue Sep 27, 2019 · 0 comments
Closed

Create an Ingress object for Metalk8s UI #1799

nootal opened this issue Sep 27, 2019 · 0 comments
Labels
complexity:medium Something that requires one or few days to fix topic:networking Networking-related issues topic:ui UI-related issues

Comments

@nootal
Copy link
Contributor

nootal commented Sep 27, 2019

Blocked by #1796

Component:

'kubernetes', 'ingress'

Why this is needed:

Because we want to expose the Metalk8s UI using an Ingress, so it could be available on something like: <some_control_plane_network_ip_address>(:80)/gui

What should be done:

Create such an object and make sure it targets the proper Ingress class for the control plane network.

Implementation proposal (strongly recommended):

Probably some stuff to solve to make it work on the /gui route. To be done also in the UI to make sure it works (right now it seems the UI can not support such a route as a prefix).
Should we keep the nodePort service? I don't know.

Test plan:

  • UI should be available on <some_control_plane_network_ip_address>(:80)/gui
  • Everything should work as before
@nootal nootal added topic:networking Networking-related issues moonshot topic:ui UI-related issues complexity:medium Something that requires one or few days to fix labels Sep 27, 2019
@nootal nootal mentioned this issue Sep 27, 2019
Closed
NicolasT added a commit that referenced this issue Sep 27, 2019
@NicolasT
salt, ui: deploy UI using *Ingress*es
2380366 
The Kubernetes API, SaltAPI, Prometheus and the actual UI are now
exposed using the `nginx-control-plane` *Ingress* controller, and as
such accessible through the control-plane network IP of the 'bootstrap'
node, port 8443.

Fixes: #1602
See: #1602
Fixes: #1797
See: #1797
Fixes: #1799
See: #1799
Fixes: #1800
See: #1800
NicolasT added a commit that referenced this issue Sep 29, 2019
@NicolasT
salt, ui: deploy UI using *Ingress*es
01d3285 
The Kubernetes API, SaltAPI, Prometheus and the actual UI are now
exposed using the `nginx-control-plane` *Ingress* controller, and as
such accessible through the control-plane network IP of the 'bootstrap'
node, port 8443.

Fixes: #1602
See: #1602
Fixes: #1797
See: #1797
Fixes: #1799
See: #1799
Fixes: #1800
See: #1800
NicolasT added a commit that referenced this issue Sep 30, 2019
@NicolasT
salt, ui: deploy UI using *Ingress*es
dc22e16 
The Kubernetes API, SaltAPI, Prometheus and the actual UI are now
exposed using the `nginx-control-plane` *Ingress* controller, and as
such accessible through the control-plane network IP of the 'bootstrap'
node, port 8443.

Note: this also updates Cypress to a (for now) unreleased version,
because the current released version doesn't support self-signed TLS
certificates when using an IP-based host as a test target (which is the
case in our setup). This was reported upstream in
cypress-io/cypress#771 and fixed in
cypress-io/cypress#4947. The information as to
how to install an unreleased version of Cypress I got from
cypress-io/cypress#4525.

Fixes: #1602
See: #1602
Fixes: #1797
See: #1797
Fixes: #1799
See: #1799
Fixes: #1800
See: #1800
See: cypress-io/cypress#4947
See: cypress-io/cypress#771
See: cypress-io/cypress#4525
NicolasT added a commit that referenced this issue Sep 30, 2019
@NicolasT
salt, ui: deploy UI using *Ingress*es
484444d 
The Kubernetes API, SaltAPI, Prometheus and the actual UI are now
exposed using the `nginx-control-plane` *Ingress* controller, and as
such accessible through the control-plane network IP of the 'bootstrap'
node, port 8443.

Note: this also updates Cypress to a (for now) unreleased version,
because the current released version doesn't support self-signed TLS
certificates when using an IP-based host as a test target (which is the
case in our setup). This was reported upstream in
cypress-io/cypress#771 and fixed in
cypress-io/cypress#4947. The information as to
how to install an unreleased version of Cypress I got from
cypress-io/cypress#4525.

Fixes: #1602
See: #1602
Fixes: #1797
See: #1797
Fixes: #1799
See: #1799
Fixes: #1800
See: #1800
See: cypress-io/cypress#4947
See: cypress-io/cypress#771
See: cypress-io/cypress#4525
NicolasT added a commit that referenced this issue Oct 1, 2019
@NicolasT
salt, ui: deploy UI using *Ingress*es
86d4f90 
The Kubernetes API, SaltAPI, Prometheus and the actual UI are now
exposed using the `nginx-control-plane` *Ingress* controller, and as
such accessible through the control-plane network IP of the 'bootstrap'
node, port 8443.

Note: this also updates Cypress to a (for now) unreleased version,
because the current released version doesn't support self-signed TLS
certificates when using an IP-based host as a test target (which is the
case in our setup). This was reported upstream in
cypress-io/cypress#771 and fixed in
cypress-io/cypress#4947. The information as to
how to install an unreleased version of Cypress I got from
cypress-io/cypress#4525. We also ensure all
shared libraries this version of Cypress uses are installed in the test
environment.

Fixes: #1602
See: #1602
Fixes: #1797
See: #1797
Fixes: #1799
See: #1799
Fixes: #1800
See: #1800
See: cypress-io/cypress#4947
See: cypress-io/cypress#771
See: cypress-io/cypress#4525
NicolasT added a commit that referenced this issue Oct 1, 2019
@NicolasT
salt, ui: deploy UI using *Ingress*es
39b7887 
The Kubernetes API, SaltAPI, Prometheus and the actual UI are now
exposed using the `nginx-control-plane` *Ingress* controller, and as
such accessible through the control-plane network IP of the 'bootstrap'
node, port 8443.

Note: this also updates Cypress to a (for now) unreleased version,
because the current released version doesn't support self-signed TLS
certificates when using an IP-based host as a test target (which is the
case in our setup). This was reported upstream in
cypress-io/cypress#771 and fixed in
cypress-io/cypress#4947. The information as to
how to install an unreleased version of Cypress I got from
cypress-io/cypress#4525. We also ensure all
shared libraries this version of Cypress uses are installed in the test
environment.

Fixes: #1602
See: #1602
Fixes: #1797
See: #1797
Fixes: #1799
See: #1799
Fixes: #1800
See: #1800
See: cypress-io/cypress#4947
See: cypress-io/cypress#771
See: cypress-io/cypress#4525
NicolasT added a commit that referenced this issue Oct 1, 2019
@NicolasT
salt, ui: deploy UI using *Ingress*es
98b7171 
The Kubernetes API, SaltAPI, Prometheus and the actual UI are now
exposed using the `nginx-control-plane` *Ingress* controller, and as
such accessible through the control-plane network IP of the 'bootstrap'
node, port 8443.

Note: this also updates Cypress to a (for now) unreleased version,
because the current released version doesn't support self-signed TLS
certificates when using an IP-based host as a test target (which is the
case in our setup). This was reported upstream in
cypress-io/cypress#771 and fixed in
cypress-io/cypress#4947. The information as to
how to install an unreleased version of Cypress I got from
cypress-io/cypress#4525. We also ensure all
shared libraries this version of Cypress uses are installed in the test
environment.

Fixes: #1602
See: #1602
Fixes: #1797
See: #1797
Fixes: #1799
See: #1799
Fixes: #1800
See: #1800
See: cypress-io/cypress#4947
See: cypress-io/cypress#771
See: cypress-io/cypress#4525
@bert-e bert-e closed this as completed in d9c6024 Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
complexity:medium Something that requires one or few days to fix topic:networking Networking-related issues topic:ui UI-related issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nootal