Open FedericoAntoniazzi opened 4 months ago
You are using an outaded distro and furyctl version, you should update to the latest.
Apart from that, in the ingress module certManager must be configured, even if the nginx is none.
ingress:
baseDomain: internal.example.dev
# configurations for the nginx ingress controller package
nginx:
# type defines if the nginx should be configured as single or dual (internal + external) or none, with none no ingress controller will be deployed and also no ingress resource will be created
type: none
# the tls section defines how the tls for the ingresses should be managed
tls:
# provider can be certManager, secret
provider: certManager
# configuration for the cert-manager package
certManager:
# the configuration for the clusterIssuer that will be created
clusterIssuer:
# the name of the clusterIssuer
name: letsencrypt-fury
# the email used during issuing procedures
email: example@sighup.io
# you can configure the clusterIssuer by specifing type (can be only http01) or custom solvers
type: http01
The fury version should be v1.27.5 and the furyctl version should be 0.28.0
Hi Samuele,
In this scenario, I'm operating in a cluster that may not have internet connectivity in the future and no ports exposed on the internet. Is it possible to disable the default issuer in favor of a self-signed one?
Back to the original issue, spec.distribution.modules.ingress.certManager
is not marked as mandatory in the schema
Scenario
I have a
furyctl.yaml
file for an OnPremises installation, which currently needs the CNI only:I made sure everything was okay by validating the config
But then, when running the apply, I got the following error:
I also tried setting the parameter
--force all
but the error persists.