New answers tagged

1

We're using a self-hosted gitlab, nexus and Jenkins (controller) and both are hard installs on CentOS7. Jenkins agent is a remote CentOS7. That approach made the most sense to us as opposed to breaking out the whole automated pipeline shebang to deploy gitlab/jenkins/nexus. Gitlab/Jenkins/Nexus are part of the foundation of our CICD infrastructure so it made ...


2

This isn't really an ArgoCD thing. Keel is a good tool to help keep your images updated across the cluster and is super easy to implement. Basically, you'd just add some annotations to your manifest. metadata: annotations: keel.sh/policy: force keel.sh/trigger: poll keel.sh/pollSchedule: "@every 10m" It may be worth noting that ...


1

Google Support tracked down the issue down for us: this issue appears to have been caused by a known Issue affecting Konnectivity, under some circumstances a memory leak could occur, in the case of your cluster, this appears to end up causing connection timeouts after some time, this issue has already been addressed on the Konnectivity network proxy [1], ...


0

From the same page: The steps to integrate ALB and NLB with API Gateway are identical. Which follows by a sentence with a link to a documentation for an ALB ingress, including prerequisites for VPC subnets and EKS resources. Yes, you have to create one unless you'd want to configure ALB manually instead of using Ingress manifests inside k8s.


0

This is a very broad question (and BTW you have a typo in the title, it should say ECS not ECR). In terms of general positioning this may be a good starting point. Given in the title you mention "hybrid" deployments you may be interested in investigating and investigating ECS Anywhere and EKS Anywhere. They are both coming in 2021.


0

Not sure if complete reinstall is a valid option for you, but for me this helped: sudo minikube delete After delete is finished, minikube start again


0

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]


0

service is a cluster-wide object. In each node, kube-proxy will create iptable load balancing entry with all available pod's IP based on selector for a service. So NLB will distributed traffic evenly among all nodes. Then each will loadbalance the traffic to all available pods using round robin algorithm. We will have those traffic distributed among all pods ...


0

The ConfigMap and Annotation configuration have different purposes. As per nginx-configuration/configmap/#ssl-protocols: Sets the SSL protocols to use. The default is: TLSv1.2 TLSv1.3 ngx_http_ssl_module.html#ssl_protocols Context: http, server i.e., enable the specified protocols to your Nginx Controller. client --ssl-protocols-> controller --> ...


0

We have been using elastic/helm-charts for more than a year for our product, and it is easy to manage and scale on-demand. Let me know if you need any help in deploying the helm chart.


Top 50 recent answers are included