Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

How to do maintenance work in kubernetes cluster

A
Amritpal last edited by

We just moved to kubernetes, but the engineer that helped launch it is on paternity leave before we had hoped (never trust a baby not to be eager!).

Now we're trying to do maintenance tasks and one off work and having nodes get killed in the middle of things.

I've looked at using kubernetes jobs for this, but that's overkill. We don't want to write manifest files for everything.

We just need long lived shell access to do this and that.

What's the pattern for this so your maintenance task doesn't get killed?
Reply Quote 0
1 Reply Last reply
N
nishika last edited by
We were https://github.com/freelawproject/courtlistener/issues/2079#issuecomment-1145998549 by following the rules for when a node is terminated. According to the https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-types-of-pods-can-prevent-ca-from-removing-a-node , there are a number of ways that pods can prevent the cluster autoscaler from removing a node. One type of pod is:

Pods that are not backed by a controller object (so not created by deployment, replica set, job, stateful set etc).

So our solution is to create a pod in that way via a manifest file. This lets us have a pod named maintenance that sticks around and isn't killed by the cluster autoscaler:
```
---
apiVersion: v1
kind: Pod
metadata:
  name: maintenance
  namespace: blah
  labels:
    type: maintenance
spec:
  containers:
    - name: web
      image: whatever
      imagePullPolicy: IfNotPresent
      command: [bash]
      stdin: true
      tty: true
```
Reply Quote 0
1 Reply Last reply

2
Posts

0
Views

Suggested Topics

How to introduce(join) new worker node to an existing k8s cluster with selective scheduling only
Continuous Integration and Delivery (CI, CD) • kubernetes kubeadm • • Demir

2

0
Votes

2
Posts

1
Views

J

Possibly you are looking for this feature which is closed with no action since there are ways to work around this problem. kubeadm already allows to set taints for the joining node using the configuration file at join time (check my other answer for details on how to do that) One Other way to achieve this is by running join as usual but taking few extra steps as below after join 1) After successful join , Force Drain the new node to make sure it removes unwanted pod which might have scaled to it post join operation kubectl drain --force 2) Drain command will auto cordon off the node. (Note : also consider special handling to remove any daemonset which might have scaled to this node after join) 3) Now Taint the new node as needed and then uncordon it 4) Add nodeselector plus tolerance to pods you want to be scheduled on this new node. Logs of above steps for reference are listed below. On below example i have joined a new node-02 and assume that some pod were scaled in an existing deployment so new node got used immediately on join, so before adding we need drain action and then taint the node so going forward no scheduling can be done unless pod has tolerance to the taint added Nodes Before Drain or Taint $ kubectl get all -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES pod/nginx-86c57db685-8cdkx 1/1 Running 0 27s 192.168.58.120 k8s-node02-calico <none> <none> pod/nginx-86c57db685-xnh6q 1/1 Running 0 65s 192.168.182.78 k8s-node01-calico <none> <none> NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 2d <none> NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR deployment.apps/nginx 2/2 2 2 65s nginx nginx app=nginx NAME DESIRED CURRENT READY AGE CONTAINERS IMAGES SELECTOR replicaset.apps/nginx-86c57db685 2 2 2 65s nginx nginx app=nginx,pod-template-hash=86c57db685 Drain The node $ kubectl drain k8s-node02-calico node/k8s-node02-calico cordoned evicting pod "nginx-86c57db685-8cdkx" pod/nginx-86c57db685-8cdkx evicted node/k8s-node02-calico evicted $ kubectl get nodes NAME STATUS ROLES AGE VERSION k8s-master-calico Ready master 2d v1.17.2 k8s-node01-calico Ready <none> 2d v1.17.2 k8s-node02-calico Ready,SchedulingDisabled <none> 2d v1.17.2 Taint the new node $ kubectl taint node k8s-node02-calico newnode=nobodyallowed:NoSchedule node/k8s-node02-calico tainted Now we are good to uncordon the node, no more pods should be able to use this noe unless they add toleration to the new taint. $ kubectl uncordon k8s-node02-calico node/k8s-node02-calico uncordoned $ kubectl get nodes NAME STATUS ROLES AGE VERSION k8s-master-calico Ready master 2d v1.17.2 k8s-node01-calico Ready <none> 2d v1.17.2 k8s-node02-calico Ready <none> 2d v1.17.2 We test by scaling the deployment and nothign should be added on node02 $ kubectl scale deployment --replicas=3 nginx deployment.apps/nginx scaled $ kubectl get all -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES pod/nginx-86c57db685-vm8ql 1/1 Running 0 3m30s 192.168.182.75 k8s-node01-calico <none> <none> pod/nginx-86c57db685-xnh6q 1/1 Running 0 10m 192.168.182.78 k8s-node01-calico <none> <none> pod/nginx-86c57db685-zh2sj 1/1 Running 0 8m19s 192.168.182.76 k8s-node01-calico <none> <none> NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 2d <none> NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR deployment.apps/nginx 3/3 3 3 10m nginx nginx app=nginx NAME DESIRED CURRENT READY AGE CONTAINERS IMAGES SELECTOR replicaset.apps/nginx-86c57db685 3 3 3 10m nginx nginx app=nginx,pod-template-hash=86c57db685
Single Configmap for several services
Software Programming • kubernetes • • emmalee

2

0
Votes

2
Posts

0
Views

I think you can ask him as environement when you set up Deploy, for example:apiVersion: apps/v1 kind: Deployment metadata: name: frontend spec: template: spec: containers: - image: some-image imagePullPolicy: Always name: frontend env: - name: BACKEND_URL valueFrom: configMapKeyRef: key: BACKEND_URL name: urls-config PS Code above is not Polish, describes only the pitching of the container on environement
R

How's the countess filtering the external_labels prometheus?
Software Programming • kubernetes devops prometheus grafana • • Raziyah00

2

0
Votes

2
Posts

0
Views

sum(container_memory_usage_bytes{image!='', kuber="dev"}/1024/1024) by (kubernetes_io_hostname) But it's not for all the expressions that it's worth kuber=dev." It'd be best to do different dates in the graphana, but it works in the Victoriametrics cluster configuration and only. https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#url-format Maybe as an option, I'll put on every Cubber Victoriametrics and I'll take the metrics.
E

Gitworkflow and testing short lived feature branches in Openshift/Kubernetes
Continuous Integration and Delivery (CI, CD) • git kubernetes microservices cicd openshift • • emerson

2

0
Votes

2
Posts

1
Views

D

I'm not altogether sure if there actually is a problem you're trying to solve, or whether you are looking for confirmation that you are on the right track. Some thoughts: Internally openshift should be able to allocate dedicated pods Sure. Add a post-build step in your CI pipeline which does the following: Fashion a .yaml or .json description of that pod (or rather, DeploymentConfig). How/where you do that depends on your architecture - if each of your microservices has exactly the same port (i.e., all listening on 80 or 443), then you only need a central template for that, and basically only inject the name (containing the microservice name and the feature branch name) and the git source URL for it. The file can of course contain multiple OpenShift objects (i.e., the DeploymentConfig and a Route, maybe). oc apply it, OpenShift will build an image and start a pod for it. and they should be disposed once merged with develop branch Add a post-merge step which does the same in reverse, i.e. oc delete ... for every component of the original .yaml. Probably this is easiest if you give a branch-based label to each of the components, so you don't need to keep track of which you have applied in the first place. another problem with this approach is running integrated test or if services have dependency with consumer apis. If a service involved in an integrated test has state, then you indeed need to fire up a new pod/volume for each test run. If your integration test depends on external state, then you also need to manage that somehow. Both of these aspects are true anyways, no matter how you architect your solution. In these cases, you would probably do well to not start deployments right out of your individual CI pipelines, but do a "big" deployment when you start your integration test (i.e., deploy all individual microservices like described above, but also inject an ID for your current integration test run into all their names, so everything stays unique). Modifying the service name based on feature branch is not a good idea. Why not? If you wish to have a pod running for every feature branch, then you need to do it that way, period. It would certainly force you to do some kind of dependency injection (i.e., if you are testing one service A which needs another service B, then you have to tell A which B-feature it should take. But you need to do that anyway, in some form or fashion; as far as I can understand, you are trying to make the services (their branches) independent from each other, and I also assume from your question that you have one service per git repository (i.e., one service per branch) so you need to have them running per-branch.
How do I implement user authentication and management in Kubernetes?
Continuous Integration and Delivery (CI, CD) • authentication kubernetes ingress api gateway • • Demir

2

0
Votes

2
Posts

1
Views

E

I'm trying to architect a micro-service application, that runs in Kubernetes. It consists of several RESTful APIs. I want a central point to implement authentication for these APIs. This is a good idea. So what I'm looking for is a/the way to have central authentication in Kubernetes for users accessing the APIs. I would also require to be able to programmatically add users to this auth layer, so I can have users sign themselves up for access. Just to make it clear: Kubernetes is a container orchestrator, e.g. a way to manage your services. It consists of a control plane (think management of apps) and a data plane (think your apps and customer traffic). Both parts may require proper authentication and authorization. When it comes to your "business idea" - it is about the data plane - here this problem is orthogonal to the platform (e.g. Kubernetes or Heroku) that you run your apps on. So think how you should solve your problem with Microservice architecture, and not so much about Kubernetes. In my product, users would be able to sign themselves up on a website. Signing up would have to give them access to the API's. The most common protocol for this nowadays is to use OpenID Connect - that is the protocol behind both e.g. Google Accounts and Microsoft Azure AD. What you need is an OpenID Connect provider implementation. The most commonly used open source implementation is Keycloak. Remember, this kind of service is stateful and you will need a database as well. Instead of setting up your own OpenID Connect provider, you could also let the user use an account that he already has, e.g. a Google Account or Twitter Account - it depends on your use case. I've seen ingress controllers that do central auth, but I haven't found if they support programmatically adding accounts. I've also seen API gateway software that might do what I want, but I'm not sure if and if so, which ones can run in Kubernetes. What you talk about here is mostly validation of authentication and this is sometimes done using "auth aware ingress controllers". With OpenID Connect protocol, the user send a JWT-token as proof of authentication, and you could redirect unauthenticated users to your Open ID Connect provider.
S

Waiting for Solr to load
Continuous Integration and Delivery (CI, CD) • docker kubernetes • • Saumya

2

0
Votes

2
Posts

1
Views

E

This has worked - the following query has to return content-type application/xml: /solr/COLLECTION/select?q=*:*&rows=0
C

Scheduling a build using Kubernetes
Continuous Integration and Delivery (CI, CD) • kubernetes openshift kubectl • • charlenef

2

0
Votes

2
Posts

1
Views

According the documentation you're giving, you need to remove run-build from the command : $ oc run NAME --image=<image> \ [--generator=<resource>] \ [--port=<port>] \ [--replicas=<replicas>] \ [--dry-run=<bool>] \ [--overrides=<inline_json>] \ [options]
K

Kubernetes - unable to login to Dashboard
Continuous Integration and Delivery (CI, CD) • kubernetes • • kalyn

2

0
Votes

2
Posts

1
Views

K

how we can extract the certificates from the kubeconfig file: Locate your kubeconfig or config file which you use to run kubectl commands. If you have used my Vagrant file above, you can find it on /etc/kubernetes/admin.conf You need to export a single file (.p12) with the following two certificates: the client-certificate-data, and the client-key-data. My example runs the command on /home/vagrant. If you run this command on macOS, be sure to change the base64 -d to base64 -D $ grep 'client-certificate-data' ~/.kube/config | head -n 1 | awk '{print $2}' | base64 -d >> kubecfg.crt $ grep 'client-key-data' ~/.kube/config | head -n 1 | awk '{print $2}' | base64 -d >> kubecfg.key $ openssl pkcs12 -export -clcerts -inkey kubecfg.key -in kubecfg.crt -out kubecfg.p12 Import the kubecfg.p12 certificate, reopen your browser, and visit the Kubernetes Dashboard URL. Accept any warning and you should see the authentication page. You can skip the login and check you are not able to perform any task. The following steps have been copied from the Kubernetes Dashboard wiki page (Creating-sample-user) 1- Create service account cat <<EOF | kubectl create -f - apiVersion: v1 kind: ServiceAccount metadata: name: admin-user namespace: kube-system EOF >> 2- Create ClusterRoleBinding cat <<EOF | kubectl create -f - apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: admin-user roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: cluster-admin subjects: - kind: ServiceAccount name: admin-user namespace: kube-system EOF >> 3- Get the Bearer Token. Once you run the following command, copy the token value which you will use on the following step. $ kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep admin-user | awk '{print $1}') 4- Come back to your browser and choose token on the login page. You will need to paste the token value you have copied on the previous step. 5- Click “SIGN IN” and you should be able to see your Kubernetes Dashboard fully operational.
D

Kubernetes used to orchestrate Containerized Machines
Continuous Integration and Delivery (CI, CD) • docker kubernetes • • derk

2

0
Votes

2
Posts

1
Views

S

You should look at DaemonSets. You can configure it so that the Pods runs on each node of your Kubernetes cluster. Each individual Pod (running your Linux machine) can be exposed to outside network using the IP address of the node on which it is running. My need is more targeted to expose an entire machine on a precise static IP and not just a port. Before getting into further explanation, I should point out that there is nothing like exposing entire machines. Access to any machine is always through a combination of IP address and Port. So you should decide based on which port you would like to access on the container. Example: Let's say I have a 3 node Kubernetes cluster, I can create a DaemonSet with the application/image of my choice. Below names/details are imaginary, but should give an idea on the mapping. ubuntu-daemonset-pod-xyz k8s-node-1 192.168.2.1 ubuntu-daemonset-pod-abc k8s-node-2 192.168.2.2 ubuntu-daemonset-pod-hij k8s-node-3 192.168.2.3 The Pods above can be "exposed" on the IP address of the node on which it is running. That is: ubuntu-daemonset-pod-xyz on 192.168.2.1.
B

How to connect GCP Load balancer to Kubernetes cluster(single node cluster)
Continuous Integration and Delivery (CI, CD) • kubernetes load balance gcp • • baileigh

2

0
Votes

2
Posts

1
Views

R

You can use the GCP HTTP(S) Load balancer. Since you are running a kubernetes cluster (Assuming you are using GKE), GKE uses Google compute VM instance groups which can be put behind a load balancer as target group. You can follow the below steps to setup a load balancer and put your kubernetes node behind a load balancer. Login to GCP console and go to NETWORKING > Network Services > Load balancing Click on Create Load Balancer at the top of the page. Click on Start Configuration for HTTP(s) Load balancing Select From Internet to my VMs if you want to access it from public internet and click continue Give a Name to your load balancer Click on Backend Configuration and Select Backend services (from drop down) > Create a backend service Give a name to backend service and select the other parameters appropriately. Select Instance groups in Backend type. In the New backend section, select the kubernetes instance group name from the drop down. After selecting the proper instance group, you can enter the ports which will accept the requests. You can modify other things if required. At the end, click Create. Next you can setup Host and Path rules if you need any. Next, you have to configure Frontend configuration which will be your frontend to accept the requests on the port and send it to the backend target group which we configured in the step 8. Once all the configurations are done, click on Create to create your load balancer. If everything was setup correctly, you should be able to access the contents from the load balancer endpoint.
R

How To Determine Min/Max Resources For Kubernetes Pods?
Continuous Integration and Delivery (CI, CD) • kubernetes • • rosemadder

2

0
Votes

2
Posts

1
Views

A

The DevOps toolkit 2.3 book by Victor Farcic goes into some detail on this. What You Should Understand You as a developer specify whatever requests/limits you like initially. These values have no baring on reality. In order to get "real" values, you must monitor your application's real resource usage. This is best done through a monitoring tool like prometheus, instana, datadog etc. E.g. in instana, I can see that I have 512MB set up for a pod's requests, 2G for its limits, but the pod only has one container currently taking 57MB. But I can't just use 60MB as a value now... I need to load test my application and see how it behaves under real/stressed circumstances. Then you review these values and you can adjust the requests/limits accordingly. Determine Usage Without a Monitoring Tool You can use some kubectl commands to get these values as a one off (it's annoying at scale). Here is an example of a different app I have running. Notice that requests/limits are set to 1/4-2 CPUs and 4G-8G memory. But the container is really using almost no CPU and 1.198G memory. If I load tested this and those values did not move up, I would need to change them. But I have load tested it and know that they would go up towards these realistic requests/limits, so it's okay. $ kubectl describe pod -n gazelle gazelle-ws-0-0-1-6d67cffcf-lvlhk ... Limits: cpu: 2 memory: 8Gi Requests: cpu: 250m memory: 4Gi $ kubectl top pod gazelle-ws-0-0-1-6d67cffcf-lvlhk -n gazelle --containers POD NAME CPU(cores) MEMORY(bytes) gazelle-ws-0-0-1-6d67cffcf-lvlhk gazelle-ws 5m 1198Mi
How to add rules to Kubernetes NGINX Ingress controller from different yml definitions?
Continuous Integration and Delivery (CI, CD) • nginx kubernetes architecture ingress microservices • • Demir

2

0
Votes

2
Posts

1
Views

T

I was able to combine your two example files by first converting them to JSON. foo.json { "apiVersion": "extensions/v1beta1", "kind": "Ingress", "metadata": { "name": "nginx-ingress" }, "spec": { "tls": [ { "hosts": [ "foo.bar.com" ], "secretName": "tls-secret" } ], "rules": [ { "host": "foo.bar.com", "http": { "paths": [ { "path": "/", "backend": { "serviceName": "foo-web-svc", "servicePort": 80 } }, { "path": "/api", "backend": { "serviceName": "foo-rest-svc", "servicePort": 80 } } ] } } ] } } baz.json { "apiVersion": "extensions/v1beta1", "kind": "Ingress", "metadata": { "name": "nginx-ingress" }, "spec": { "tls": [ { "hosts": [ "baz.bar.com" ], "secretName": "tls-secret" } ], "rules": [ { "host": "baz.bar.com", "http": { "paths": [ { "path": "/", "backend": { "serviceName": "baz-web-svc", "servicePort": 80 } }, { "path": "/api", "backend": { "serviceName": "baz-rest-svc", "servicePort": 80 } } ] } } ] } } You can then combine the rules for each by using jq. levi@La-Tower:~$ jq 'reduce inputs as $i (.; .spec.rules += $i.spec.rules)' foo.json baz.json { "apiVersion": "extensions/v1beta1", "kind": "Ingress", "metadata": { "name": "nginx-ingress" }, "spec": { "tls": [ { "hosts": [ "foo.bar.com" ], "secretName": "tls-secret" } ], "rules": [ { "host": "foo.bar.com", "http": { "paths": [ { "path": "/", "backend": { "serviceName": "foo-web-svc", "servicePort": 80 } }, { "path": "/api", "backend": { "serviceName": "foo-rest-svc", "servicePort": 80 } } ] } }, { "host": "baz.bar.com", "http": { "paths": [ { "path": "/", "backend": { "serviceName": "baz-web-svc", "servicePort": 80 } }, { "path": "/api", "backend": { "serviceName": "baz-rest-svc", "servicePort": 80 } } ] } } ] } } While yaml is more common JSON is perfectly valid for the Kubernetes API. All credit for the jq logic goes to @Jeff Mercado and his answer.
R

Is it required to move a domain to Google DNS in order to use certbot in kubernetes on Google Cloud platform?
Continuous Integration and Delivery (CI, CD) • dns kubernetes google cloud platform certbot • • Rossere

2

0
Votes

2
Posts

1
Views

R

@euank indicated that it is not required to create a DNS record on GCP in order to make it work. https://github.com/jetstack/cert-manager/issues/399
C

Managed MySQL cluster - similar solution for a private cloud
Continuous Integration and Delivery (CI, CD) • mysql kubernetes vmware • • chanisef

2

0
Votes

2
Posts

1
Views

K

There shouldn't be any reason why you can't. I think that the issue would be in getting the memory management correct on the host. The orchestration would be the same. Here's some resources: https://dev.mysql.com/doc/mysql-cluster-excerpt/8.0/en/faqs-mysql-cluster.html#qandaitem-B-1-13 https://www.digitalocean.com/community/tutorials/how-to-create-a-multi-node-mysql-cluster-on-ubuntu-18-04. It shows with docker as well. it shouldn't be hard to apply to vmware or k8s. https://towardsdatascience.com/high-availability-mysql-cluster-with-load-balancing-using-haproxy-and-heartbeat-40a16e134691/ https://www.cockroachlabs.com/docs/stable/orchestrate-a-local-cluster-with-kubernetes.html to set up k8s locally.
O

Does Kubernetes internal networking keep traffic to co-located Pods where possible?
Continuous Integration and Delivery (CI, CD) • dns kubernetes networking • • Oba22

2

0
Votes

2
Posts

1
Views

B

This looks to be answered on offcail docs here NodeLocal DNSCache improves Cluster DNS performance by running a dns caching agent on cluster nodes as a DaemonSet. With this architecture, Pods will reach out to the dns caching agent running on the same node, thereby avoiding iptables DNAT rules and connection tracking. Having a local cache will help improve the latency. Image Reference : https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/#architecture-diagram

How to do maintenance work in kubernetes cluster

Suggested Topics

How to introduce(join) new worker node to an existing k8s cluster with selective scheduling only Continuous Integration and Delivery (CI, CD) • kubernetes kubeadm • • Demir

Single Configmap for several services Software Programming • kubernetes • • emmalee

How's the countess filtering the external_labels prometheus? Software Programming • kubernetes devops prometheus grafana • • Raziyah00

Gitworkflow and testing short lived feature branches in Openshift/Kubernetes Continuous Integration and Delivery (CI, CD) • git kubernetes microservices cicd openshift • • emerson

How do I implement user authentication and management in Kubernetes? Continuous Integration and Delivery (CI, CD) • authentication kubernetes ingress api gateway • • Demir

Waiting for Solr to load Continuous Integration and Delivery (CI, CD) • docker kubernetes • • Saumya

Scheduling a build using Kubernetes Continuous Integration and Delivery (CI, CD) • kubernetes openshift kubectl • • charlenef

Kubernetes - unable to login to Dashboard Continuous Integration and Delivery (CI, CD) • kubernetes • • kalyn

Kubernetes used to orchestrate Containerized Machines Continuous Integration and Delivery (CI, CD) • docker kubernetes • • derk

How to connect GCP Load balancer to Kubernetes cluster(single node cluster) Continuous Integration and Delivery (CI, CD) • kubernetes load balance gcp • • baileigh

How To Determine Min/Max Resources For Kubernetes Pods? Continuous Integration and Delivery (CI, CD) • kubernetes • • rosemadder

How to add rules to Kubernetes NGINX Ingress controller from different yml definitions? Continuous Integration and Delivery (CI, CD) • nginx kubernetes architecture ingress microservices • • Demir

Is it required to move a domain to Google DNS in order to use certbot in kubernetes on Google Cloud platform? Continuous Integration and Delivery (CI, CD) • dns kubernetes google cloud platform certbot • • Rossere

Managed MySQL cluster - similar solution for a private cloud Continuous Integration and Delivery (CI, CD) • mysql kubernetes vmware • • chanisef

Does Kubernetes internal networking keep traffic to co-located Pods where possible? Continuous Integration and Delivery (CI, CD) • dns kubernetes networking • • Oba22

How to introduce(join) new worker node to an existing k8s cluster with selective scheduling only
Continuous Integration and Delivery (CI, CD) • kubernetes kubeadm • • Demir

Single Configmap for several services
Software Programming • kubernetes • • emmalee

How's the countess filtering the external_labels prometheus?
Software Programming • kubernetes devops prometheus grafana • • Raziyah00

Gitworkflow and testing short lived feature branches in Openshift/Kubernetes
Continuous Integration and Delivery (CI, CD) • git kubernetes microservices cicd openshift • • emerson

How do I implement user authentication and management in Kubernetes?
Continuous Integration and Delivery (CI, CD) • authentication kubernetes ingress api gateway • • Demir

Waiting for Solr to load
Continuous Integration and Delivery (CI, CD) • docker kubernetes • • Saumya

Scheduling a build using Kubernetes
Continuous Integration and Delivery (CI, CD) • kubernetes openshift kubectl • • charlenef

Kubernetes - unable to login to Dashboard
Continuous Integration and Delivery (CI, CD) • kubernetes • • kalyn

Kubernetes used to orchestrate Containerized Machines
Continuous Integration and Delivery (CI, CD) • docker kubernetes • • derk

How to connect GCP Load balancer to Kubernetes cluster(single node cluster)
Continuous Integration and Delivery (CI, CD) • kubernetes load balance gcp • • baileigh

How To Determine Min/Max Resources For Kubernetes Pods?
Continuous Integration and Delivery (CI, CD) • kubernetes • • rosemadder

How to add rules to Kubernetes NGINX Ingress controller from different yml definitions?
Continuous Integration and Delivery (CI, CD) • nginx kubernetes architecture ingress microservices • • Demir

Is it required to move a domain to Google DNS in order to use certbot in kubernetes on Google Cloud platform?
Continuous Integration and Delivery (CI, CD) • dns kubernetes google cloud platform certbot • • Rossere

Managed MySQL cluster - similar solution for a private cloud
Continuous Integration and Delivery (CI, CD) • mysql kubernetes vmware • • chanisef

Does Kubernetes internal networking keep traffic to co-located Pods where possible?
Continuous Integration and Delivery (CI, CD) • dns kubernetes networking • • Oba22