jonashackt

brew install kind helm kubectl

jonashackt

apiVersion: v2
type: application
name: crossplane
version: 0.0.0 # unused
appVersion: 0.0.0 # unused
dependencies:
  - name: crossplane
    repository: https://charts.crossplane.io/stable
    version: 1.8.1

jonashackt

$ docker images | grep vsc
vsc-microservice-ui-nuxt-js-fc70bec7c72be6f886987af8b1c42d94-features latest edd6d935f397 17 hours ago 1.44GB
vsc-microservice-ui-nuxt-js-fc70bec7c72be6f886987af8b1c42d94 latest 6f80ad49fca6 6 weeks ago 1.23GB

jonashackt

// Use 'forwardPorts' to make a list of ports inside the container available locally.
"forwardPorts": [3000],

jonashackt

# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.234.0/containers/typescript-node/.devcontainer/base.Dockerfile

# [Choice] Node.js version: 18, 16, 14, 18-bullseye, 16-bullseye, 14-bullseye
ARG VARIANT="16-bullseye"
FROM mcr.microsoft.com/vscode/devcontainers/typescript-node:0-${VARIANT}

# [Optional] Uncomment this section to install additional OS packages.
# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
#     && apt-get -y install --no-install-recommends <your-package-list-here>

jonashackt

{
  "name": "Node.js & TypeScript",
  "build": {
    "dockerfile": "Dockerfile",
    // Update 'VARIANT' to pick a Node version: 18, 16, 14.
    "args": {
      "VARIANT": "16-bullseye"
    }
  },
  "extensions": [

jonashackt

What is GitOps

Great intro https://www.gitops.tech/

For me the difference between Push-based (also CI-Ops, like traditional CI/CD pipelines) and Pull-based (operator takes over) Deployments was the key here.

Tools

https://www.dev-insider.de/gitops-tools-in-der-uebersicht-a-943715/

jonashackt

Show Git Graph (like IntelliJ)

see https://stackoverflow.com/questions/37899765/how-can-i-view-the-git-history-in-visual-studio-code

My favorite Plugin: https://marketplace.visualstudio.com/items?itemName=mhutchie.git-graph

jonashackt

Paketo.io / CloudNativeBuildPack created Container image doesn't have curl installed - and this is for good reasons (see https://stackoverflow.com/a/65393843/4964553 & https://blog.sixeyed.com/docker-healthchecks-why-not-to-use-curl-or-iwr/).

So we need another aproach... As suggested we should use the container inherited language (here: Java/JDK) to write our own healthcheck.

Creating our own Java-based Healthcheck without curl

So let's look at this great article https://mflash.dev/blog/2021/03/01/java-based-health-check-for-docker/ , where Naiyer explains how to write a simple healthcheck based on Java 11+

Here's my adoption leveraging an argument to provide a specific port. Just look into HealthCheck.java:

jonashackt

# Samples:
https://github.com/buildpacks/samples


# We can override the default ENTRYPOINT in a CNB build container
see https://buildpacks.io/docs/app-developer-guide/run-an-app/#user-provided-shell-process

So we need to know the default launch process of a CNB build Spring Boot container - and then add the needed installation command