tamalsaha

$ helm install kubedb appscode/kubedb \
  --version v2022.03.28 \
  --namespace kubedb --create-namespace \
  --set kubedb-provisioner.enabled=true \
  --set kubedb-ops-manager.enabled=true \
  --set kubedb-autoscaler.enabled=true \
  --set kubedb-dashboard.enabled=true \
  --set kubedb-schema-manager.enabled=true \
 --set-file global.license=/path/to/the/license.txt \

tamalsaha

---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: goldpinger-serviceaccount
  namespace: default
---
apiVersion: apps/v1
kind: DaemonSet
metadata:

tamalsaha

Kubernetes (v1.23.4)
System.IO.IOException: No space left on device : '/home/runner/actions-runner/_diag/Worker_20220330-123646-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite() at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args) System.IO.IOException: No space left on device : '/home/runner/actions-runner/_diag/Worke

tamalsaha

apiVersion: kubedb.com/v1alpha2
kind: Postgres
metadata:
  name: confluence-db-copy
  namespace: platform-atlassian
spec:
  allowedSchemas:
    namespaces:
      from: Same
  clientAuthMode: md5

tamalsaha

apiVersion: kubedb.com/v1alpha2
kind: Postgres
metadata:
  name: demo-pg
  namespace: demo
spec:
  version: "11.11-test"
  coordinator:
    resources:
      limits:

tamalsaha

// +genclient - generate default client verb functions (create, update, delete, get, list, update, patch, watch and depending on the existence of .Status field in the type the client is generated for also updateStatus).

// +genclient:nonNamespaced - all verb functions are generated without namespace.

// +genclient:onlyVerbs=create,get - only listed verb functions will be generated.

// +genclient:skipVerbs=watch - all default client verb functions will be generated except watch verb.

// +genclient:noStatus - skip generation of updateStatus verb even thought the .Status field exists.

tamalsaha

{
  "annotations": {
    "list": [
      {
        "builtIn": 1,
        "datasource": "-- Grafana --",
        "enable": true,
        "hide": true,
        "iconColor": "rgba(0, 211, 255, 1)",
        "name": "Annotations & Alerts",

tamalsaha

# kind cluster
LICENSE_FILE=/Users/tamal/Downloads/kubedb-enterprise-license-efa6308c-ecfd-480e-a11c-2722fecf6b8d.txt

helm upgrade -i opscenter-core appscode/opscenter-core \
  -n kubeops --create-namespace \
  --set kube-ui-server.enabled=false \
  --set panopticon.enabled=true \
  --set panopticon.monitoring.serviceMonitor.labels.release=kube-prometheus-stack \
  --set-file panopticon.license=$LICENSE_FILE

tamalsaha

apiVersion: meta.k8s.appscode.com/v1alpha1
kind: Render
request:
  block:
    displayMode: List
    fieldPath: '{.response.dashboards[0].panels}'
    kind: Connection
    query:
      raw: |
        request:

tamalsaha

Caveat: I am writing this based on my understanding of the tools I tried at the time. Things are constantly changing in k8s world. So, it is possible some of the comments here are outdated.

I don't mean to hurt anyone's feelings. I am trying to find tools that help me solve our customer problems. I am trying to make a decision that can help us deliver our products to our customers today.

Data vs Code: I think data, ie, YAML is the right layer for coordination among k8s ecosystem tools. YAML works great as the "wire format". But for human users a higher level YAML generation tool (aka, code) is often needed.

Our use-cases: We make k8s operators that we sell to users. In the beginning, we would offer users a curl | bash script. Over time, users started asking for customizations in installer scripts that became hard to do with just scripts. Also, scripts don't work in Windows. So, we started supporting both script and helm charts. Over time it became quite hard to keep these in sync and test. So,