| --- | |
| apiVersion: apps/v1 | |
| kind: Deployment | |
| metadata: | |
| name: packet-cloud-controller-manager | |
| namespace: kube-system | |
| labels: | |
| app: packet-cloud-controller-manager | |
| spec: | |
| replicas: 1 |
Linode's nginx-ingress docs (https://www.linode.com/docs/kubernetes/how-to-deploy-nginx-ingress-on-linode-kubernetes-engine/) don't have instructions on using the proxy protocol with nginx-ingress at https://kubernetes.github.io/ingress-nginx/deploy/
The helm chart linked in the Linode docs is deprecated.
The following was taken from https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.40.2/deploy/static/provider/do/deploy.yaml with hints from:
| #!/usr/bin/env bash | |
| CMD=metal | |
| # METAL_ORGANIZATION_ID=(the one you want to clean), otherwise defaults to metal cli settings) | |
| $CMD project get | \ | |
| awk '/\s*(tfacc|GHACTION|ansible)/ {print $2}' | \ | |
| while read proj; do | |
| $CMD devices get -p $proj | \ | |
| awk '/tfacc|ansible|GHACTION/ {print $2}' | \ | |
| xargs -n1 $CMD device delete -f --id ; | |
| $CMD project delete -f --id $proj ; |
| #cloud-config | |
| phone_home: | |
| url: "http://tinkerbell.ewr1.packet.net/phone-home" | |
| post: | |
| - instance_id | |
| tries: 5 | |
| autoinstall: | |
| version: 1 | |
| # use interactive-sections to avoid an automatic reboot | |
| #interactive-sections: |
| #!ipxe | |
| dhcp net0 | |
| set release 4.7 | |
| set zstream 0 | |
| set arch x86_64 | |
| set ignition-url https://metadata.platformequinix.com/userdata | |
| #set coreos-url https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/${release}/${release}.${zstream} |
| diff --git a/protos/hardware/hardware.proto b/protos/hardware/hardware.proto | |
| index 3601801..3ac88c0 100644 | |
| --- a/protos/hardware/hardware.proto | |
| +++ b/protos/hardware/hardware.proto | |
| @@ -6,36 +6,58 @@ package github.com.tinkerbell.tink.protos.hardware; | |
| import "google/api/annotations.proto"; | |
| +// The HardwareService services provides access to data describing the compute | |
| +// and networking profiles of the hardware available to accept workflows. |
| import packet | |
| import json | |
| import os | |
| from pathlib import Path | |
| label="[email protected]" | |
| manager = packet.Manager(auth_token=os.environ["APIKEY"]) | |
| #manager.get_ssh_key("4405413a-8da6-4e56-9c4f-07e532d7a024").delete() | |
| keys = manager.list_ssh_keys() |
| apiVersion: packet.crossplane.io/v1alpha2 | |
| kind: Provider | |
| metadata: | |
| name: packet-provider | |
| spec: | |
| credentialsSecretRef: | |
| key: key | |
| name: packet-creds | |
| namespace: packet-test | |
| projectID: b12cc31b-170c-4986-bb55-2489f7c22a88 |
Stacks may depend on access to other custom resources in the API. These
dependencies are provided in the dependsOn field of the Stack spec.
Each dependency results in an RBAC Rule authorizing the service account used by the Stack controller to access the resources defined in the Stack.
The following Stack body would result in the Stack's controller running under a