-
-
Notifications
You must be signed in to change notification settings - Fork 201
Description
I am using K3s version 1.17 as follows:
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.5+k3s1", GitCommit:"58ebdb2a2ec5318ca40649eb7bd31679cb679f71", GitTreeState:"clean", BuildDate:"2020-05-06T23:42:07Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/arm64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.5+k3s1", GitCommit:"58ebdb2a2ec5318ca40649eb7bd31679cb679f71", GitTreeState:"clean", BuildDate:"2020-05-06T23:42:07Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/arm64"}
And now, I am getting this error when I do the make deploy command:
unable to recognize "manifests/ingress-alertmanager.yaml": no matches for kind "Ingress" in version "networking.k8s.io/v1"
unable to recognize "manifests/ingress-grafana.yaml": no matches for kind "Ingress" in version "networking.k8s.io/v1"
unable to recognize "manifests/ingress-prometheus.yaml": no matches for kind "Ingress" in version "networking.k8s.io/v1"
make: *** [Makefile:40: deploy] Error 1
I checked the Api-resources and Api-versions and I see I have both:
networking.k8s.io/v1
networking.k8s.io/v1beta1
This just started happening. I deployed it like 2 months ago with no issue. I redownloaded the whole package and I can't deploy it now.
vars.jsonnet:
{
_config+:: {
namespace: 'monitoring',
},
// Enable or disable additional modules
modules: [
{
// After deployment, run the create_gmail_auth.sh script from scripts dir.
name: 'smtpRelay',
enabled: false,
file: import 'modules/smtp_relay.jsonnet',
},
{
name: 'armExporter',
enabled: true,
file: import 'modules/arm_exporter.jsonnet',
},
{
name: 'upsExporter',
enabled: false,
file: import 'modules/ups_exporter.jsonnet',
},
{
name: 'metallbExporter',
enabled: false,
file: import 'modules/metallb.jsonnet',
},
{
name: 'nginxExporter',
enabled: false,
file: import 'modules/nginx.jsonnet',
},
{
name: 'traefikExporter',
enabled: true,
file: import 'modules/traefik.jsonnet',
},
{
name: 'elasticExporter',
enabled: false,
file: import 'modules/elasticsearch_exporter.jsonnet',
},
{
name: 'speedtestExporter',
enabled: false,
file: import 'modules/speedtest_exporter.jsonnet',
},
],
k3s: {
enabled: true,
master_ip: ['192.168.1.5'],
},
// Domain suffix for the ingresses
suffixDomain: '192.168.1.5.nip.io',
// Additional domain suffixes for the ingresses.
// For example suffixDomain could be an external one and this a local domain.
additionalDomains: [],
// If TLSingress is true, a self-signed HTTPS ingress with redirect will be created
TLSingress: true,
// If UseProvidedCerts is true, provided files will be used on created HTTPS ingresses.
// Use a wildcard certificate for the domain like ex. "*.192.168.99.100.nip.io"
UseProvidedCerts: false,
TLSCertificate: importstr 'server.crt',
TLSKey: importstr 'server.key',
// Persistent volume configuration
enablePersistence: {
// Setting these to false, defaults to emptyDirs.
prometheus: false,
grafana: false,
// If using a pre-created PV, fill in the names below. If blank, they will use the default StorageClass
prometheusPV: '',
grafanaPV: '',
// If required to use a specific storageClass, keep the PV names above blank and fill the storageClass name below.
storageClass: '',
// Define the PV sizes below
prometheusSizePV: '2Gi',
grafanaSizePV: '20Gi',
},
// Configuration for Prometheus deployment
prometheus: {
retention: '15d',
scrapeInterval: '30s',
scrapeTimeout: '30s',
},
grafana: {
// Grafana "from" email
from_address: '[email protected]',
// Plugins to be installed at runtime.
//Ex. plugins: ['grafana-piechart-panel', 'grafana-clock-panel'],
plugins: [],
//Ex. env: [ { name: 'http_proxy', value: 'host:8080' } ]
env: []
},
}
- Did you change any other file? No:
I am not able to access anything since the namespaces are not created.