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

Document how to install and access UI from EKS #170

Open
jwmatthews opened this issue Mar 27, 2023 · 3 comments
Open

Document how to install and access UI from EKS #170

jwmatthews opened this issue Mar 27, 2023 · 3 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@jwmatthews
Copy link
Member

jwmatthews commented Mar 27, 2023 •
edited
Loading

Let's walk through an install of Konveyor to an EKS cluster and document the steps and any tweaks needed for getting Ingress configured.

In particular, let's ensure we cover both flows of auth enabled/disabled, so we can be sure the workflow is accessible when keycloack is enabled.
@jwmatthews jwmatthews mentioned this issue Mar 27, 2023
Closed
@jwmatthews jwmatthews mentioned this issue Apr 9, 2023
Closed
@jwmatthews
Copy link
Member Author

We now have the means of easily spinning up AWS EKS clusters with Ansible + CLIs for (eksctl + aws) to aid other contributors for development/testing. You will need to supply your own AWS Credentials.

https://github.com/konveyor/hack_env_helpers/tree/main/aws/eks

The above will provision an EKS cluster and configure both the EBSCI AddOn and the ALB Ingress controller. Roughly ~20 mins to setup cluster and ~5-10 minutes to install software to test it out, including OLM + Konveyor.

This gives us the needed starting point so we have an EKS cluster with dynamic PV provisioning (RWO only, no RWX) and Ingress via AWS LoadBalancer.

First thing noticed is issue #184 where the Ingress we create has a hard assumption of nginx for Ingress.

spec:
  ingressClassName: nginx

@jwmatthews jwmatthews mentioned this issue Apr 14, 2023
Merged
jwmatthews added a commit that referenced this issue Apr 26, 2023
@jwmatthews
✨ Support for Amazon Load Balancer Ingress controller (#197)
00792cd 
Fixes #184 
Fixes #167 (confirmed working with `feature_auth_required: true`)
Relates to #170

These changes allow us to deploy Konveyor onto an Amazon EKS cluster
that uses the Amazon recommended Amazon Load Balancer ingress opposed to
'nginx'.

I deployed the EKS cluster for testing using this newly developed
automation:
https://github.com/konveyor/hack_env_helpers/tree/main/aws/eks

I captured notes while exploring ALB Ingress here for debugging
purposes:
https://gist.github.com/jwmatthews/d492a4944c83dc3f2d016187d53d13b2

---------

Signed-off-by: John Matthews <jwmatthews@gmail.com>
jmontleon pushed a commit to jmontleon/tackle2-operator that referenced this issue May 23, 2023
@jwmatthews @jmontleon
✨ Support for Amazon Load Balancer Ingress controller (konveyor#197)
0ebfd5c 
Fixes konveyor#184
Fixes konveyor#167 (confirmed working with `feature_auth_required: true`)
Relates to konveyor#170

These changes allow us to deploy Konveyor onto an Amazon EKS cluster
that uses the Amazon recommended Amazon Load Balancer ingress opposed to
'nginx'.

I deployed the EKS cluster for testing using this newly developed
automation:
https://github.com/konveyor/hack_env_helpers/tree/main/aws/eks

I captured notes while exploring ALB Ingress here for debugging
purposes:
https://gist.github.com/jwmatthews/d492a4944c83dc3f2d016187d53d13b2

---------

Signed-off-by: John Matthews <jwmatthews@gmail.com>
(cherry picked from commit 00792cd)
@jmontleon jmontleon mentioned this issue May 23, 2023
Merged
jmontleon pushed a commit to jmontleon/tackle2-operator that referenced this issue May 23, 2023
@jwmatthews @jmontleon
✨ Support for Amazon Load Balancer Ingress controller (konveyor#197)
1407faf 
Fixes konveyor#184 
Fixes konveyor#167 (confirmed working with `feature_auth_required: true`)
Relates to konveyor#170

These changes allow us to deploy Konveyor onto an Amazon EKS cluster
that uses the Amazon recommended Amazon Load Balancer ingress opposed to
'nginx'.

I deployed the EKS cluster for testing using this newly developed
automation:
https://github.com/konveyor/hack_env_helpers/tree/main/aws/eks

I captured notes while exploring ALB Ingress here for debugging
purposes:
https://gist.github.com/jwmatthews/d492a4944c83dc3f2d016187d53d13b2

---------

Signed-off-by: John Matthews <jwmatthews@gmail.com>
jmontleon added a commit that referenced this issue May 23, 2023
@jmontleon @jwmatthews
✨ Support for Amazon Load Balancer Ingress controller (#197) (#235)
8d8e198 
Fixes #184
Fixes #167 (confirmed working with `feature_auth_required: true`)
Relates to #170

These changes allow us to deploy Konveyor onto an Amazon EKS cluster
that uses the Amazon recommended Amazon Load Balancer ingress opposed to
'nginx'.

I deployed the EKS cluster for testing using this newly developed
automation:
https://github.com/konveyor/hack_env_helpers/tree/main/aws/eks

I captured notes while exploring ALB Ingress here for debugging
purposes:
https://gist.github.com/jwmatthews/d492a4944c83dc3f2d016187d53d13b2

---------

Signed-off-by: John Matthews <jwmatthews@gmail.com>
(cherry picked from commit 00792cd)

Co-authored-by: John Matthews <jwmatthews@gmail.com>
@djzager
Copy link
Member

djzager commented Feb 14, 2024

@jwmatthews @jmontleon Looks like PRs have merged that maybe fixed this issue. Where does it stand?

@djzager djzager added this to Planning Feb 14, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Feb 14, 2024
@djzager djzager added triage/needs-information Indicates an issue needs more information in order to work on it. kind/documentation Categorizes issue or PR as related to documentation. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels Feb 14, 2024
@konveyor-ci-bot konveyor-ci-bot bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 14, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@dymurray dymurray moved this from 🆕 New to ✅ Done in Planning Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
Planning
Status: ✅ Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jwmatthews @djzager