Ricardo Zanini ricardozanini

How to solve Minikube coreDNS i/o timeout on a Mac

Just a note about restarting a Minikube instance running with podman on a Mac.

You might have seem a problem in the coreDNS pods being unable to resolve naming.

Try using podman driver and the CRI-O container runtime instead of Docker runtime:

minikube start --container-runtime=cri-o

Apply the resources.yaml file kubectl apply -f resources.yaml -n <namespace>
This will deploy a default InMemory Broker, a Trigger filtering by source: /from/ping and a custom event display, so we can see the content-type header.
Run the following command from your terminal to create a temporary container to run curl:

kubectl run curl --image=radial/busyboxplus:curl -i --tty --rm

	apiVersion: v1
	kind: Namespace
	metadata:
	labels:
	control-plane: controller-manager
	name: nexus-operator-system
	---
	apiVersion: apiextensions.k8s.io/v1beta1
	kind: CustomResourceDefinition
	metadata:

	id: fraudhandling
	name: Fraud Handling
	start: FraudHandling
	version: "1.0"
	events:
	- kind: produced
	name: FraudEvaluation
	type: orders.fraudEvaluation
	source: fraudEvaluation
	states:

	{
	"id": "fahrenheit_to_celsius",
	"name": "Fahrenheit to Celsius Conversion Flow",
	"version": "v1.0",
	"functions": [
	{
	"name": "multiplication",
	"resource": "/",
	"type": "rest",
	"metadata": {

	openapi: 3.0.3
	info:
	title: Generated API
	version: "1.0"
	paths:
	/:
	post:
	operationId: cloudEventListener
	requestBody:
	content:

	# other fields omitted for brevity
	networking:
	expose: true
	exposeAs: "Ingress"
	host: "nexus.example.com"

	$ kubectl get nexus –n nexus

	NAME EXPOSE AS UPDATE DISABLED STATUS REASON MAVEN PUBLIC URL
	nexus3 Route OK http://nexus3.nexus/repository/maven-public/

	$ oc get routes –n nexus

	NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD
	nexus3 nexus3-nexus.apps-crc.testing nexus3 http None