https://containers.dev an open spec that extends container definition to also include dev environment configuration including:
- packages
- lifecycle automation
- processes
- IDE configurations
- remote connection
- port forwarding
https://containers.dev an open spec that extends container definition to also include dev environment configuration including:
# Source: https://gist.github.com/6fb3e7da327df9203d9d4c184fcb5831 | |
############################################################################## | |
# Combining Argo CD (GitOps), Crossplane (Control Plane), And Kubevela (OAM) # | |
# https://youtu.be/eEcgn_gU3SM # | |
############################################################################## | |
# Referenced videos: | |
# - Argo CD - Applying GitOps Principles To Manage Production Environment In Kubernetes: https://youtu.be/vpWQeoaiRM4 | |
# - Cloud-Native Apps With Open Application Model (OAM) And KubeVela: https://youtu.be/2CBu6sOTtwk |
The package that linked you here is now pure ESM. It cannot be require()
'd from CommonJS.
This means you have the following choices:
import foo from 'foo'
instead of const foo = require('foo')
to import the package. You also need to put "type": "module"
in your package.json and more. Follow the below guide.await import(…)
from CommonJS instead of require(…)
.# Source: https://gist.github.com/a156975ae372bf15284e15c489aab4aa | |
########################################################################## | |
# Crossplane # | |
# Using Kubernetes API and GitOps to manage Infrastructure as Code (IaC) # | |
# https://youtu.be/n8KjVmuHm7A # | |
########################################################################## | |
# Referenced videos: | |
# - Argo CD - Applying GitOps Principles To Manage Production Environment In Kubernetes: https://youtu.be/vpWQeoaiRM4 |
# Source: https://gist.github.com/48f44d3974db698d3127f52b6e7cd0d3 | |
########################################################### | |
# Automation of Everything # | |
# How To Combine Argo Events, Workflows, CD, and Rollouts # | |
# https://youtu.be/XNXJtxkUKeY # | |
########################################################### | |
# Requirements: | |
# - k8s v1.19+ cluster with nginx Ingress |
This was initially posted in an kubernetes-sigs/kustomize issue.
We are using Kustomize's vars
feature. Initially we didn't understand how to use it for our purpose, but it is a 100% fit. One example is our Ingress resource, which looks like this:
# file: base/ingress.yaml
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: services
GitHub allows automated builds using GitHub Actions. A commonly asked question is how to release artifacts (packaged Java jars) built by Maven and Gradle to The Central Repository. The GitHub Actions documentation provides only part of the answer.
So, first, configure your Maven project for staging artifacts to The Central Repository, by reading through Configuring Your Project for Deployment and following those steps. Please make sure that the maven-gpg-plugin is configured to prevent gpg
from using PIN entry programs, as follows:
<configuration>
<gpgArguments>
<arg>--pinentry-mode</arg>
loopback