11 of 11 Istio Jobs in the North West

Developing of RESTful API services & understanding of API Gateways (e.g. APIGEE) Building applications utilising container technologies e.g. Docker Managing application deployed to Kubernetes clusters, Istio & Helm Cloud: GCP, GKE, IaC (Terraform) Build Tools & DevOps principles: Git, Maven, Jenkins CI/CD, Nexus, SonarQube It would be great if you also More ❯

problem-solving skills. Strong communication and documentation skills. Desirable: Experience with cloud-based Kubernetes services (e.g., EKS ). Knowledge of service mesh technologies (e.g., Istio , Linkerd ). Experience with monitoring and logging tools (e.g., Prometheus, Grafana, ELK stack). Familiarity with CI/CD pipelines and containerization best practices. Kubernetes More ❯

problem-solving skills. Strong communication and documentation skills. Desirable: Experience with cloud-based Kubernetes services (e.g., EKS ). Knowledge of service mesh technologies (e.g., Istio, Linkerd). Experience with monitoring and logging tools (e.g., Prometheus, Grafana, ELK stack). Familiarity with CI/CD pipelines and containerization best practices. Kubernetes More ❯

problem-solving skills. Strong communication and documentation skills. Desirable: Experience with cloud-based Kubernetes services (e.g., EKS ). Knowledge of service mesh technologies (e.g., Istio, Linkerd). Experience with monitoring and logging tools (e.g., Prometheus, Grafana, ELK stack). Familiarity with CI/CD pipelines and containerization best practices. Kubernetes More ❯

into Redhat/Windriver For OpenShift, experience with their TNC reference architecture is a big plus From a networking perspective, MetalLB and service mesh (Istio). For Storage, experience with Pure and Portworx would be good. For the IaaS component OpenStack is being used, both Redhat and Windriver Excellent written More ❯

into Redhat/Windriver For OpenShift, experience with their TNC reference architecture is a big plus From a networking perspective, MetalLB and service mesh (Istio). For Storage, experience with Pure and Portworx would be good. For the IaaS component OpenStack is being used, both Redhat and Windriver Excellent written More ❯

into Redhat/Windriver For OpenShift, experience with their TNC reference architecture is a big plus From a networking perspective, MetalLB and service mesh (Istio). For Storage, experience with Pure and Portworx would be good. For the IaaS component OpenStack is being used, both Redhat and Windriver Excellent written More ❯

into Redhat/Windriver For OpenShift, experience with their TNC reference architecture is a big plus From a networking perspective, MetalLB and service mesh (Istio). For Storage, experience with Pure and Portworx would be good. For the IaaS component OpenStack is being used, both Redhat and Windriver Excellent written More ❯

into Redhat/Windriver For OpenShift, experience with their TNC reference architecture is a big plus From a networking perspective, MetalLB and service mesh (Istio). For Storage, experience with Pure and Portworx would be good. For the IaaS component OpenStack is being used, both Redhat and Windriver Excellent written More ❯

into Redhat/Windriver For OpenShift, experience with their TNC reference architecture is a big plus From a networking perspective, MetalLB and service mesh (Istio). For Storage, experience with Pure and Portworx would be good. For the IaaS component OpenStack is being used, both Redhat and Windriver Excellent written More ❯

into Redhat/Windriver For OpenShift, experience with their TNC reference architecture is a big plus From a networking perspective, MetalLB and service mesh (Istio). For Storage, experience with Pure and Portworx would be good. For the IaaS component OpenStack is being used, both Redhat and Windriver Excellent written More ❯