-
Notifications
You must be signed in to change notification settings - Fork 75
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
docs: Helm install on GKE, AKS, and EKS #2777
Conversation
Creating namespace initially makes more sense. Since it can be used during the database installation. Also removing sudo makes kubeconfig flag unnecessary too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work. Go over my comments please and also check grammar and spelling
fix indentation so that copying is simpler
docs: Helm install on EKS
enabled: true | ||
``` | ||
|
||
So if your desired configuration has no-FQDN and LDAP, the final `override.yaml` file will look something like that: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where id the nginx-ingress section go that you asked the user to add above?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am covering no-FQDN, so it there's no nginx-ingress section. only LBaddr is needed.
In the other override.yaml example, which covers mysql and registered fqdn, it has the nginx-ingress section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nginx ingress is needed in both cases . I'm not following
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nginx:
ingress:
enabled: true
path: /
hosts:
- demoexample.jans.org #CHANGE-THIS to the FQDN used for Jans
tls:
- secretName: tls-certificate
hosts:
- demoexample.jans.org #CHANGE-THIS to the FQDN used for Jans
```
enabled: true | ||
``` | ||
|
||
So if your desired configuration has no-FQDN and LDAP, the final `override.yaml` file will look something like that: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nginx-ingress section that you asked the user to add is missing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you still need to add this
nginx:
ingress:
enabled: true
path: /
hosts:
- demoexample.jans.org #CHANGE-THIS to the FQDN used for Jans
tls:
- secretName: tls-certificate
hosts:
- demoexample.jans.org #CHANGE-THIS to the FQDN used for Jans
````
enabled: true | ||
``` | ||
|
||
So if your desired configuration has no-FQDN and LDAP, the final `override.yaml` file will look something like that: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you still need to add this
nginx:
ingress:
enabled: true
path: /
hosts:
- demoexample.jans.org #CHANGE-THIS to the FQDN used for Jans
tls:
- secretName: tls-certificate
hosts:
- demoexample.jans.org #CHANGE-THIS to the FQDN used for Jans
````
enabled: true | ||
``` | ||
|
||
So if your desired configuration has no-FQDN and LDAP, the final `override.yaml` file will look something like that: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nginx:
ingress:
enabled: true
path: /
hosts:
- demoexample.jans.org #CHANGE-THIS to the FQDN used for Jans
tls:
- secretName: tls-certificate
hosts:
- demoexample.jans.org #CHANGE-THIS to the FQDN used for Jans
```
|
||
2. Create a [Resource Group](https://learn.microsoft.com/en-us/azure/aks/learn/quick-kubernetes-deploy-cli#create-a-resource-group) | ||
``` | ||
az group create --name myResourceGroup --location eastus |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
give the resource group a good unique name like maybe janssen
|
||
3. Create an [AKS cluster](https://learn.microsoft.com/en-us/azure/aks/learn/quick-kubernetes-deploy-cli#create-aks-cluster) such as the following example: | ||
``` | ||
az aks create -g myResourceGroup -n myAKSCluster --enable-managed-identity --node-vm-size NODE_TYPE --node-count 2 --enable-addons monitoring --enable-msi-auth-for-monitoring --generate-ssh-keys |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lets use the name janssen
across our examples. You can call things like example-janssen
for our clusters and groups
* docs: Helm install on GKE * docs: fix to yaml * docs: remove unnecessary sudo, kubeconfig flag and create namespace Creating namespace initially makes more sense. Since it can be used during the database installation. Also removing sudo makes kubeconfig flag unnecessary too * docs: fix file name * docs: fix * docs: fix indentation fix indentation so that copying is simpler * docs: rephrase * docs: Helm install on EKS docs: Helm install on EKS * fix: typo * docs: EKS fix * docs: fix mistake in GKE too * docs: Helm install on AKS * docs: fix
* fix(config-api): client creation exception * fix(config-api): client creations exception * fix(config-api): issues fixed 2743, 2755 and 2689 * fix(config-api): change to use fido2 app config model * fix(config-api): change to use fido2 app config model * docs(config-api): swagger fix for script enum * fix: avoid NPE when configuration is missing #2857 (#2863) * Initial commit IDM, IAG, 2FA Portal (#2873) initial commit * fix(image): multiple dynamic scopes created when using 2 replicas (#2871) * feat: for file based scripts check both script revision and file (#2878) modification time #2877 Co-authored-by: Yuriy Movchan <Yuriy.Movchan@gmail.com> * feat(jans-auth-server): added token exchange support to client #2518 (#2855) And added native sso http test. * feat: ssa revoke endpoint (#2865) * docs: update ubuntu.md (#2870) * docs: Helm install on GKE, AKS, and EKS (#2777) * docs: Helm install on GKE * docs: fix to yaml * docs: remove unnecessary sudo, kubeconfig flag and create namespace Creating namespace initially makes more sense. Since it can be used during the database installation. Also removing sudo makes kubeconfig flag unnecessary too * docs: fix file name * docs: fix * docs: fix indentation fix indentation so that copying is simpler * docs: rephrase * docs: Helm install on EKS docs: Helm install on EKS * fix: typo * docs: EKS fix * docs: fix mistake in GKE too * docs: Helm install on AKS * docs: fix * fix(jans-auth-server): fix language metadata format (#2883) * fix(jans-auth-server): fix language metadata format * fix(jans-auth-server): fix language metadata format * Initial checkin: RBAC, central authz (#2884) Starting point for these topics * fix(config-api): swagger update for enum and error handling Co-authored-by: Jose <bonustrack310@gmail.com> Co-authored-by: Mike Schwartz <mike@gluu.org> Co-authored-by: Isman Firmansyah <iromli@users.noreply.github.com> Co-authored-by: Yuriy M <95305560+yuremm@users.noreply.github.com> Co-authored-by: Yuriy Movchan <Yuriy.Movchan@gmail.com> Co-authored-by: YuriyZ <yzabrovarniy@gmail.com> Co-authored-by: Milton Ch <86965029+Milton-Ch@users.noreply.github.com> Co-authored-by: mzico <mohib@gluu.org> Co-authored-by: misba7 <amromisba7@gmail.com> Co-authored-by: Javier Rojas <javier.rojas.blum@gmail.com>
* docs: Helm install on GKE * docs: fix to yaml * docs: remove unnecessary sudo, kubeconfig flag and create namespace Creating namespace initially makes more sense. Since it can be used during the database installation. Also removing sudo makes kubeconfig flag unnecessary too * docs: fix file name * docs: fix * docs: fix indentation fix indentation so that copying is simpler * docs: rephrase * docs: Helm install on EKS docs: Helm install on EKS * fix: typo * docs: EKS fix * docs: fix mistake in GKE too * docs: Helm install on AKS * docs: fix
Prepare
Description
Target issue
closes #issue-number-here
Implementation Details
Test and Document the changes