Because the ingressgateway only open their ports when at least one downstream "ingressed" service is deployed, we want to deploy a very simple (useless even) service that will ensure the availability of the ingress gateway node ports. This was done for dse-k8s-eqiad during setup as well.
Description
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T362105 EPIC: OpenSearch on K8s (formerly Mutualized opensearch cluster) - FY25/26 WE4.2.6 | |||
| Resolved | • Stevemunene | T396478 EPIC: Build dse-k8s-codfw Kubernetes cluster | |||
| Resolved | • Stevemunene | T404433 Deploy an echoserver service on dse-k8s-codfw behind ingress |
Event Timeline
Change #1187805 had a related patch set uploaded (by Stevemunene; author: Stevemunene):
[operations/deployment-charts@master] dse-k8s: Define echoserver namespace for dse-k8s-codfw
Change #1187806 had a related patch set uploaded (by Stevemunene; author: Stevemunene):
[operations/deployment-charts@master] dse-k8s: Define helmfiles for echoserver in dse-k8s-codfw
Change #1187805 merged by jenkins-bot:
[operations/deployment-charts@master] dse-k8s: Define echoserver namespace for dse-k8s-codfw
Change #1188307 had a related patch set uploaded (by Stevemunene; author: Stevemunene):
[operations/puppet@production] Add kubeconfig files for echoserver on dse-k8s
Change #1188307 merged by Stevemunene:
[operations/puppet@production] Add kubeconfig files for echoserver on dse-k8s
Change #1187806 merged by jenkins-bot:
[operations/deployment-charts@master] dse-k8s: Define helmfiles for echoserver in dse-k8s-codfw
Getting an error on the deployment which I am looking into
Error: Failed to render chart: exit status 1: WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /etc/kubernetes/echoserver-deploy-dse-k8s-codfw.config Error: rendered manifests contain a resource that already exists. Unable to continue with install: could not get information about the resource DestinationRule "echoserver-production" in namespace "echoserver": destinationrules.networking.istio.io "echoserver-production" is forbidden: User "echoserver-deploy" cannot get resource "destinationrules" in API group "networking.istio.io" in the namespace "echoserver": RBAC: clusterrole.rbac.authorization.k8s.io "allow-privileged-psp" not found Error: plugin "diff" exited with error
Change #1189634 had a related patch set uploaded (by Stevemunene; author: Stevemunene):
[operations/deployment-charts@master] dse-k8s: Deploy network policies for istio setup in codfw
Change #1189634 merged by jenkins-bot:
[operations/deployment-charts@master] dse-k8s: Deploy network policies for istio setup in codfw
Change #1189795 had a related patch set uploaded (by Stevemunene; author: Stevemunene):
[operations/dns@master] Register ingress CNAME record for the echoserver-dse-k8s-eqiad service
Echoserver deployed on dse-k8s-codfw
LAST DEPLOYED: Fri Sep 19 08:35:34 2025
NAMESPACE: echoserver
STATUS: deployed
REVISION: 1
NOTES:
Thank you for installing echoserver.
Your release is named echoserver-production.
To learn more about the release, try:
$ helm status echoserver-production
$ helm get echoserver-production
You are using minikube, which means it's really easy to access your service. Run the following
MINIKUBE_HOST=$(minikube ip)
SERVICE_PORT=$(kubectl get svc --namespace echoserver echoserver-production -o jsonpath='{.spec.ports[0].nodePort}')
curl http://${MINIKUBE_HOST}:${SERVICE_PORT}/
or alternatively in your browser using the following URL
echo http://${MINIKUBE_HOST}:${SERVICE_PORT}/
Listing releases matching ^production$
production echoserver 1 2025-09-19 08:35:34.607966927 +0000 UTC deployed echoserver-0.0.8
UPDATED RELEASES:
NAME NAMESPACE CHART VERSION DURATION
production echoserver wmf-stable/echoserver 0.0.8 9sChange #1189795 merged by Stevemunene:
[operations/dns@master] Register ingress CNAME record for the echoserver-dse-k8s-codfw service