hello-kubernetes | Example end-to-end build | Continuous Deployment library

Your ClusterIssuer refers to LetsEncrypt staging issuer. Remove that setting / the default should use their production setup. As pointed out in comments: https://acme-v02.api.letsencrypt.org/directory

Deleting the previously generated secrets or switching to new secrets should ensure your certificates would be re-generated, using the right issuer.

The staging issuer could be useful testing LetsEncrypt integration, it shouldn't be used otherwise.

You showed kubectl version. Your kubernetes version also need to be v1.20. Make sure you are using kubernetes version v1.20.

Use kubectl version for seeing both client and server version. Where client version refers to kubectl version and server version refers to kubernetes version.

As far the k8s v1.20 release note doc: Previously introduced in 1.19 behind a feature gate, SetHostnameAsFQDN is now enabled by default. More details on this behavior is available in documentation for DNS for Services and Pods

createOptions.Labels are translated into pod annotations. So you can put the required Dapr annotations as the module's labels:

metadata

name = Name will be the module name, sanitized to be a K8s identifier. namespace = The given namespace. labels = Default label set. annotations = The pod's metadata will have one fixed annotation: net.azure-devices.edge.original-moduleid = unsanitized module id from edge deployment specification. then settings.createOptions.Labels will be added to the pod's annotations.

There is no way to "opt-out" of injecting the iotedge proxy but it should be benign even if it is co-present with Dapr's injected sidecar. I've not tested this, so let us if it works for you!

This is a community wiki answer as a part of it would be based on @meaningqo comment but I would like to share some more light on this topic with a help of the official documentations.

What you were doing in the first place is not deleting a deployment but actually scaling it to 0. In order to delete a deployment or any other resource you should use the kubectl delete command:

Delete resources by filenames, stdin, resources and names, or by resources and label selector.

JSON and YAML formats are accepted. Only one type of the arguments may be specified: filenames, resources and names, or resources and label selector.

Note that:

Some resources, such as pods, support graceful deletion. These resources define a default period before they are forcibly terminated (the grace period) (...) Because these resources often represent entities in the cluster, deletion may not be acknowledged immediately.

So you may want to wait a bit before seeing the results.

Referring to your second question. There are also other options aimed to work with ReplicaSets specifically:

• Deleting a ReplicaSet and its Pods

• Deleting just a ReplicaSet

I also recommend familiarizing yourself with the whole ReplicaSet guide for better understanding of this particular topic.

Referring from docs you need to use extraPortMappings to allow the local host to make requests to the hello-kubernetes over port 80

Nginx container is using port 80 by default and you are trying to connect to port 8080 where nothing is listening and thus getting connection refused.

Take a look here at nginx conateiner Dockerfile. What port do you see?

All you need to do to make it work is to change target port like following:

It happens because you are using staging server from Let's Encrypt. The staging server is used only for tests, and after you consider it's ok you can move to production servers.

You need to create a new issuer using this examples

After change your ingress annotation to :

Please keep in mind, that resource names in Kubernetes needs to be in lower-case:

secretName

that's probably causing your issue.

You haven't specified the secrets containing your certificate: