Cannot enable knative
See original GitHub issueI can’t enable knative. It waits for istio to be ready but istio doesn’t seem to be ready. I tried to disable and enable istio again but it gives another error.
(kubeflow) user01@user-X299-WU8:/data/mhkwon/kubeflow/istio-1.8.4$ microk8s enable knative
Enabling Knative
Addon istio is already enabled.
Waiting for Istio to be ready
......................................................................................^C
Aborted!
(kubeflow) user01@user-X299-WU8:/data/mhkwon/kubeflow/istio-1.8.4$ microk8s status
microk8s is running
high-availability: no
datastore master nodes: 127.0.0.1:19001
datastore standby nodes: none
addons:
enabled:
dashboard # The Kubernetes dashboard
dns # CoreDNS
gpu # Automatic enablement of Nvidia CUDA
ha-cluster # Configure high availability on the current node
ingress # Ingress controller for external access
istio # Core Istio service mesh services
metallb # Loadbalancer for your Kubernetes cluster
metrics-server # K8s Metrics Server for API access to service metrics
storage # Storage class; allocates storage from host directory
disabled:
ambassador # Ambassador API Gateway and Ingress
cilium # SDN, fast with full network policy
fluentd # Elasticsearch-Fluentd-Kibana logging and monitoring
helm # Helm 2 - the package manager for Kubernetes
helm3 # Helm 3 - Kubernetes package manager
host-access # Allow Pods connecting to Host services smoothly
jaeger # Kubernetes Jaeger operator with its simple config
keda # Kubernetes-based Event Driven Autoscaling
knative # The Knative framework on Kubernetes.
kubeflow # Kubeflow for easy ML deployments
linkerd # Linkerd is a service mesh for Kubernetes and other frameworks
multus # Multus CNI enables attaching multiple network interfaces to pods
portainer # Portainer UI for your Kubernetes cluster
prometheus # Prometheus operator for monitoring and logging
rbac # Role-Based Access Control for authorisation
registry # Private image registry exposed on localhost:32000
traefik # traefik Ingress controller for external access
(kubeflow) user01@user-X299-WU8:/data/mhkwon/kubeflow/istio-1.8.4$ microk8s disable istio
Disabling Istio
Error from server (NotFound): namespaces "istio-system" not found
(kubeflow) user01@user-X299-WU8:/data/mhkwon/kubeflow/istio-1.8.4$ microk8s enable istio
Addon istio is already enabled.
This is the tarball. inspection-report-20210323_204727.tar.gz
I’m facing so many bugs on microk8s…
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (3 by maintainers)
Top Results From Across the Web
Cannot enable knative · Issue #2118 · canonical/microk8s
I can't enable knative. It waits for istio to be ready but istio doesn't seem to be ready. I tried to disable and...
Read more >Debugging application issues - Knative
Debugging application issues¶. If you have deployed an application but are having issues, you can use the following steps to troubleshoot the application....
Read more >Install by using the Knative Operator
To configure Knative Serving to use Kourier, add spec.ingress.kourier and spec. · Apply the YAML file for your Serving CR by running the...
Read more >Enabling auto-TLS certs - Knative
If you install and configure cert-manager, you can configure Knative to automatically obtain new TLS certificates and renew existing ones for Knative Services....
Read more >Installing Knative Serving using YAML files
Install a networking layer¶ · Configure Knative Serving to use Kourier by default by running the command: kubectl patch configmap/config-network \ --namespace ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ktsakalozos coredns isn’t running, that could be the reason why. The node is also in
NotReady
state. But calico is reported to be up.This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.