Bernardo García bgarcial

1. Analyze the reasons which kong-ingress-controller does not works with cert-manager

Some things that I can see.

When I've already created the ClusterIssuer (staging-environment) and the kong-ingress-zcrm365 ingress resource (our zcrm-custom ingress); cert-manager creates a new Ingress resource to handle the ACME http01 validation named cm-acme-http-solver-jr4fg

 ⟩ kubectl get ingress 
NAME                        HOSTS                                ADDRESS         PORTS     AGE
cm-acme-http-solver-jr4fg test1kongletsencrypt.possibilit.nl 80 33s

Installing helm and tiller

Helm is a package manager tool which allow to find, share, and use software built for Kubernetes.

Install helm from this script. There are many releases

I have an existing Virtual Network created with two subnets: aks-subnet and persistence-subnet.

My goal is to create an Azure Kubernetes Cluster inside the aks-subnet

I am creating resource groups and resources [at the subscription level][1], using the New-AzDeployment command from PowerShell core.

Like my idea is create a resource group and deploy resources to it, I have a nested template defining the resources to create in the resource group.

So I have the resource group created from the ARM template

	apiVersion: extensions/v1beta1
	kind: Ingress
	metadata:
	name: kong-ingress-zcrm365
	namespace: default
	annotations:
	kubernetes.io/ingress.class: "nginx" #new
	#certmanager.k8s.io/issuer: "letsencrypt-staging"
	#certmanager.k8s.io/acme-challenge-type: http01

	⟩ kubectl describe certificate letsencrypt-prod
	Name: letsencrypt-prod
	Namespace: default
	Labels: <none>
	Annotations: <none>
	API Version: certmanager.k8s.io/v1alpha1
	Kind: Certificate
	Metadata:
	Creation Timestamp: 2019-03-14T14:20:15Z
	Generation: 1

	---
	apiVersion: certmanager.k8s.io/v1alpha1
	kind: Issuer
	metadata:
	name: letsencrypt-prod
	spec:
	acme:
	server: https://acme-v02.api.letsencrypt.org/directory
	email: [email protected]
	privateKeySecretRef:

	⟩ kubectl describe issuers letsencrypt-prod
	Name: letsencrypt-prod
	Namespace: default
	Labels: <none>
	Annotations: kubectl.kubernetes.io/last-applied-configuration:
	{"apiVersion":"certmanager.k8s.io/v1alpha1","kind":"Issuer","metadata":{"annotations":{},"name":"letsencrypt-prod","namespace":"default"},...
	API Version: certmanager.k8s.io/v1alpha1
	Kind: Issuer
	Metadata:
	Creation Timestamp: 2019-03-14T14:03:06Z

	apiVersion: v1
	kind: Namespace
	metadata:
	name: kong

	---

	apiVersion: v1
	kind: Secret
	metadata:

	apiVersion: configuration.konghq.com/v1
	kind: KongIngress
	metadata:
	name: sandbox-ingress-zcrm365
	# namespace: default
	proxy:
	protocols:
	- http
	- https
	# path: /

-#!/bin/sh
-# based on https://gist.github.com/ipedrazas/9c622404fb41f2343a0db85b3821275d
-# delete all evicted pods from all namespaces
-kubectl get pods --all-namespaces | grep Evicted | awk '{print $2 " --namespace=" $1}' | xargs kubectl delete pod
-# delete all containers in ImagePullBackOff state from all namespaces
-kubectl get pods --all-namespaces | grep 'ImagePullBackOff' | awk '{print $2 " --namespace=" $1}' | xargs kubectl delete pod
-# delete all containers in ImagePullBackOff or ErrImagePull or Evicted state from all namespaces