| {% extends "base.html" %} | |
| {% block content %} | |
| <form method="post">{% csrf_token %} | |
| {{ forms.subscription }} | |
| <input type="submit" value="Subscribe"> | |
| </form> | |
| <form method="post">{% csrf_token %} | |
| {{ forms.contact }} | |
| <input type="submit" value="Send"> |
| #requires -version 3 | |
| function Remove-Profile { | |
| param( | |
| [string[]]$ComputerName = $env:ComputerName, | |
| [pscredential]$Credential = $null, | |
| [string[]]$Name, | |
| [ValidateRange(0,365)][int]$DaysOld = 0, | |
| [string[]]$Exclude, | |
| [switch]$IgnoreLastUseTime, | |
| [switch]$Remove |
Minio is an object storage server compatible with the S3 protocol. Head to https://minio.io/ to learn more.
Hint: You might want to use MINIO_WORM=on to pretect against accidental or malicious deletion of your backups.
Since RELEASE.2018-10-18T00-28-58Z minio supports seperate users with attached IAM policies. Instead of (or additionally to) using MINIO_WORM=on you could create a new user and attach a writeonly policy:
This is not official documentation/tooling, use with caution
This generate the Kubernetes definitions of the cattle-cluster-agent Deployment and cattle-node-agent DaemonSet, in case it's accidentally removed/server-url was changed/certficates were changed. It is supposed to run on every cluster Rancher manages. If you have custom clusters created in Rancher, see Kubeconfig for Custom clusters created in Rancher how to obtain the kubeconfig to directly talk to the Kubernetes API (as usually it doesn't work via Rancher anymore). For other clusters, use the tools provided by the provider to get the kubeconfig.
IMPORTANT: You get the cluster/node agents definitions from Rancher, and you apply them to the cluster that is created/managed so you need to switch kubeconfig to point to that cluster before applying them.
The steps below requires that you have followed the installation steps for installing K3s on RPIs.
NOTE: The following files can be found in the following repository.
Installation steps for K3s dashboard. On master node, create a folder called dashboard:
| Docker 23 + Traefik v2.9.10 and v1.7 + Let's Encrypt + Github Registry V2 ghcr.io + Updated on 12 April 2023 | |
| Content: | |
| - Ubuntu 22.04 | |
| - Docker Engine 23.0.3 | |
| - Docker Compose 2.17.2 | |
| - Traefik v1.7.18 with dnsChallenge | |
| - Traefik v2.9.9 with httpChallenge | |
| -- | |
| - Github Registry V2 ghcr.io |
Registering Rancher managed clusters in Argo CD doesn't work out of the box unless the Authorized Cluster Endpoint is used. Many users will prefer an integration of Argo CD via the central Rancher authentication proxy (which shares the network endpoint of the Rancher API/GUI). So let's find out why registering clusters via Rancher auth proxy fails and how to make it work.
Hint: If you are just looking for the solution scroll to the bottom of this page.
I created this gist on May 25, 2021. It is still an issue as of February 7th, 2025. Welcome to the future of web development. Take this Gist to rest and calm down.