connection refused for https
$ nmcli general hostname
haitmeroa.tech
$ cat deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deploy-choco
namespace: mero-ns
labels:
app: nginx-cc
spec:
replicas: 1
selector:
matchLabels:
app: nginx-cc
template:
metadata:
labels:
app: nginx-cc
spec:
containers:
- name: git-sync
image: registry.k8s.io/git-sync/git-sync:v4.2.3
volumeMounts:
- name: www-data
mountPath: /data
env:
- name: GITSYNC_REPO
value: "http://192.168.56.8:3000/rocky/chochoc.git"
- name: GIT_SYNC_BRANCH
value: "main"
- name: GITSYNC_ROOT
value: /data
- name: GIT_SYNC_DEST
value: "html"
- name: GITSYNC_ONE_TIME
value: "false"
- name: GIT_SYNC_COMMAND_AFTER
value: "nginx -s reload"
securityContext:
runAsUser: 0
- name: nginx-choco
image: nginx
ports:
- containerPort: 80
volumeMounts:
- mountPath: "/usr/share/nginx/"
name: www-data
volumes:
- name: www-data
emptyDir: {}
gitsync works fine
$ cat service.yaml
apiVersion: v1
kind: Service
metadata:
name: nginx-service
namespace: mero-ns
labels:
app: nginx-cc
spec:
type: NodePort
selector:
app: nginx-cc
ports:
- port: 80
nodePort: 30080
name: http
- port: 443
nodePort: 30443
name: https
$ cat ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: mero-ingress
namespace: mero-ns
annotations:
kubernetes.io/ingress.class: nginx
spec:
ingressClassName: nginx
tls:
- hosts:
- haitmeroa.tech
secretName: tls-secret
rules:
- host: haitmeroa.tech
http:
paths:
- backend:
service:
name: nginx-service
port:
number: 80
path: /
pathType: ImplementationSpecific
$ openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout tls.key -out tls.crt $ kubectl create secret tls tls-secret --key MyServer.key --cert MyServer.crt -n mero-ns
http service works when called via curl but connection refused for https
Curl CLUSTER-IP :80 works
Curl CLUSTER-IP:443 Connection refused
this was done on a
VM: virtual box
OS: rocky linux 9
all reference from official docs of redhat, kubernetes, git-sync github
New contributor
Trilochan Aryal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.