Monthly Archives: May 2021

ArgoCD: declarative Projects, Applications, and ArgoCD deploy from Jenkins
0 (0)

19 May 2021

An application, cluster, or repository can be created In ArgoCD from its WebUI, CLI, or by writing a Kubernetes manifest that then can be passed to kubectl to create resources. For example, Applications are Kubernetes CustomResources and described in Kubernetes CRD applications.argoproj.io: [simterm] $ kubectl get crd applications.argoproj.io NAME CREATED AT applications.argoproj.io 2020-11-27T15:55:29Z [/simterm] And… Read More: ArgoCD: declarative Projects, Applications, and ArgoCD deploy from Jenkins0 (0) »

Loading

ArgoCD: Okta integration, and user groups
0 (0)

17 May 2021

In the previous post ArgoCD: users, access, and RBAC we’ve checked how to manage users and their permissions in ArgoCD, now let’s add an SSO authentification. The idea is that we don’t add user accounts locally in the ArgoCD’s ConfigMap, but instead will use our Okta users databases and Okta will perform their authentication. And… Read More: ArgoCD: Okta integration, and user groups0 (0) »

Loading

ArgoCD: users, access, and RBAC
0 (0)

17 May 2021

ArgoCD has two types of users – local, that are set in the argocd-cm ConfigMap, and SSO. Below, we will speak about local user management, and in the next chapter will see how to integrate ArgoCD and Okta, because local users can’t be grouped in groups. See the documentation on the Local users/accounts page. For… Read More: ArgoCD: users, access, and RBAC0 (0) »

Loading

Github: Github Actions overview and ArgoCD deployment example
0 (0)

7 May 2021

Github Actions actually is very similar to the TravisCI, but have much more closer integration with Github, and even its interface is included in the Github WebUI: So, let’s take a closer look at its abilities, how to use it, and in the following posts will deploy its self-hosted runners to a Kubernetes cluster and will… Read More: Github: Github Actions overview and ArgoCD deployment example0 (0) »

Loading

Kubernetes: spec.ports[0].nodePort: Forbidden: may not be used when `type` is ‘ClusterIP’
0 (0)

5 May 2021

During applications deploy from a Helm chart described in the Istio: shared Ingress/AWS ALB, Helm chart with conditions, Istio, and ExternalDNS we are getting the “spec.ports[0].nodePort: Forbidden: may not be used when `type` is ‘ClusterIP’” error. Let’s reproduce it and find solutions with kubectl and Helm to solve it. The “spec.ports[0].nodePort: Forbidden: may not be… Read More: Kubernetes: spec.ports[0].nodePort: Forbidden: may not be used when `type` is… »

Loading