weltonrodrigo

nome
ABADIA DE GOIAS
ABADIA DOS DOURADOS
ABADIANIA
ABAETE
ABAETETUBA
ABAIARA
ABAIRA
ABARE
ABATIA

weltonrodrigo

Does Azure eventhub auto-inflates on egress?

No.

---

Yeah, that took me a long time.

The ingress rate is what makes the eventhub namespace scale, but not the consumption (the egress). Egress don't get throttled either, you'll have to keep an eye at the rate of consumption and partition limits.

weltonrodrigo

Believe it or not, when you do a kubectl completion zsh on your ~/.zshrc, kubectl actually tries to contact the cluster of the current-context.

This is nuts and I don't understand why it would make sense.

As this can easly take seconds to complete, you can force it to quickly give up by pointing it to a impossible HTTPS_PROXY like this:

On your ~/.zshrc…

weltonrodrigo

When creating an imagePullSecret with kustomize secretGenerator, you need to set type to kubernetes.io/dockerconfigjson, not Opaque.

Like:

secretGenerator:
- files:
  - .dockerconfigjson
  name: docker-pull-secret
 type: kubernetes.io/dockerconfigjson

weltonrodrigo

This message on the GKE ingress:

Warning  Translate  42m (x25 over 63m)    loadbalancer-controller  Translation failed: invalid ingress spec: service "<namespace>/<servicename>" is type "ClusterIP",
expected "NodePort" or "LoadBalancer"; service "<namespace>/<servicename>" is type "ClusterIP", expected "NodePort" or "LoadBalancer"; service "<namespace>/<servicename>" is type "ClusterIP", expected "NodePort" or "LoadBalancer"; service "<namespace>/<servicename>" is type "ClusterIP", expected "NodePort" or "LoadBalan
cer"; service "<namespace>/<servicename>" is type "ClusterIP", expected "NodePort" or "LoadBalancer"

What this actually means is that the network endpoint groups are not being created automatically, so, without a NEG, the load balancer would need an exernal ip and port to reach the pods.

You can assert that by the absence of the NEG status annotation on the ingress and also in the backend service.

weltonrodrigo

What is an error with status HTTP 470 on Azure?

This is probably Azure Firewall.

Check the body of the response, it has some debug information:

< HTTP/1.1 470 status code 470
< Date: Sun, 27 Feb 2022 04:29:17 GMT
&lt; Content-Length: 70

weltonrodrigo

Using dive (container explorer tool) with a remote docker

When using DOCKER_HOST with a remote daemon, like DOCKER_HOST=ssh:user@vm:22, you'll get an error when using dive to explore an image.

$ dive ubuntu:latest

Image Source: docker://ubuntu:latest

weltonrodrigo

import logging
import pprint
import sys
from json import dumps
from typing import List

from kafka import KafkaProducer
from kafka.errors import KafkaError
from kafka.future import Future

weltonrodrigo

package br.org.prf.azuremapsexample.controllers;

import com.azure.core.credential.AccessToken;
import com.azure.core.credential.TokenRequestContext;
import com.azure.identity.DefaultAzureCredentialBuilder;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

import reactor.core.publisher.Mono;

weltonrodrigo

#cloud-config

apt:
  sources:
    docker.list:
      source: deb [arch=amd64] https://download.docker.com/linux/ubuntu $RELEASE stable
      keyid: 9DC858229FC7DD38854AE2D88D81803C0EBFCD88

packages:
  - apt-transport-https