witty-translator-86250
04/17/2023, 9:50 AMwitty-translator-86250
04/17/2023, 9:51 AMloud-diamond-82990
04/17/2023, 10:55 AMloud-diamond-82990
04/17/2023, 12:38 PMwhite-branch-93180
04/17/2023, 1:25 PMrhythmic-painter-76998
04/17/2023, 3:01 PMbest-address-42882
04/17/2023, 3:49 PMwide-smartphone-57691
04/17/2023, 4:41 PMproud-ram-62490
04/17/2023, 5:55 PMchilly-translator-36463
04/17/2023, 6:25 PMapiVersion: apps/v1
kind: Deployment
metadata:
name: tea-deployment
labels:
app: tea
spec:
replicas: 1
selector:
matchLabels:
app: tea
template:
metadata:
labels:
app: tea
spec:
containers:
- name: tea
image: nirulabs/tea:latest
ports:
- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
name: tea-service
spec:
type: NodePort
selector:
app: tea
ports:
- port: 8082
targetPort: 80
nodePort: 30003
---
apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
kind: Ingress
metadata:
name: tea-ingress
spec:
rules:
- host: <http://example.com|example.com>
http:
paths:
- pathType: Prefix
path: "/"
backend:
service:
name: tea-service
port:
number: 8082
chilly-translator-36463
04/17/2023, 6:25 PMchilly-translator-36463
04/17/2023, 6:26 PMchilly-translator-36463
04/17/2023, 6:28 PMswift-cricket-47233
04/17/2023, 6:54 PMerror trying to reach service: dial tcp: lookup [HOSTNAME] on [COREDNS:53] no such host
. We've been able to isolate the issue to CoreDNS, and specifically one of the CoreDNS pods seems to be unable to resolve the lookup being requested...but this works a few seconds later (on the same pod). Has anybody experienced this, or does anybody have some advice/guidance on how we might fix it?stale-spring-20280
04/17/2023, 8:09 PMmammoth-kilobyte-91460
04/18/2023, 1:30 AMingress.tls.email
because the previous owner of this cluster isn't working with us anymore.
So, I tried steps 3, 4 and 5 of the official documentation but my certificate it's still the same:
https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/resources/update-rancher-certificate#3-reconfigure[…]her-deployment
I'm curious if I need to generate a LetsEncrypt certificate manually again (using certbot) and update the secret with it or how can I run a certbot server if my rancher application are running on a k8s cluster?
Please, I'm struggling with this issue for some days.busy-flag-55906
04/18/2023, 10:25 AMbusy-flag-55906
04/18/2023, 10:26 AMbusy-flag-55906
04/18/2023, 10:26 AMabundant-portugal-24141
04/18/2023, 10:57 AMabundant-portugal-24141
04/18/2023, 11:17 AM"Error: INSTALLATION FAILED: execution error at (rancher/templates/validate-psp-install.yaml:4:5): The target cluster does not have the PodSecurityPolicy API resource. Please disable PSPs in this chart before proceeding."
If I add the "global.cattle.psp.enabled=false" flag, I get an other error:
INSTALLATION FAILED: unable to build kubernetes objects from release manifest: resource mapping not found for name: "rancher" namespace: "" from "": no matches for kind "Issuer" in version "<http://cert-manager.io/v1alpha2|cert-manager.io/v1alpha2>" Ensure CRDs are installed first
Can someone please suggest what I am missing?gentle-diamond-79411
04/18/2023, 12:43 PMfuture-garden-49149
04/18/2023, 1:11 PMfuture-garden-49149
04/18/2023, 1:11 PM[ERROR] API error response 500 for POST /v3-public/activeDirectoryProviders/activedirectory?action=login. Cause: invalid server config. at least 1 server needs to be configured
future-garden-49149
04/18/2023, 1:12 PMmost-sunset-36476
04/18/2023, 2:20 PMsidecar:
dashboards:
enabled: true
label: grafana_dashboard
searchNamespace: cattle-dashboards
But i can't find the cattle-dashboards
namespace, is this a normal behavior ? Is that namespace created by default ?best-address-42882
04/18/2023, 3:11 PMbest-address-42882
04/18/2023, 8:04 PMbrash-oil-2252
04/19/2023, 10:22 AMproud-ram-62490
04/19/2023, 2:54 PM