mirror of
https://github.com/tailscale/tailscale.git
synced 2026-02-12 03:01:28 +01:00
3ec5be3f51
This file was never truly necessary and has never actually been used in the history of Tailscale's open source releases. A Brief History of AUTHORS files --- The AUTHORS file was a pattern developed at Google, originally for Chromium, then adopted by Go and a bunch of other projects. The problem was that Chromium originally had a copyright line only recognizing Google as the copyright holder. Because Google (and most open source projects) do not require copyright assignemnt for contributions, each contributor maintains their copyright. Some large corporate contributors then tried to add their own name to the copyright line in the LICENSE file or in file headers. This quickly becomes unwieldy, and puts a tremendous burden on anyone building on top of Chromium, since the license requires that they keep all copyright lines intact. The compromise was to create an AUTHORS file that would list all of the copyright holders. The LICENSE file and source file headers would then include that list by reference, listing the copyright holder as "The Chromium Authors". This also become cumbersome to simply keep the file up to date with a high rate of new contributors. Plus it's not always obvious who the copyright holder is. Sometimes it is the individual making the contribution, but many times it may be their employer. There is no way for the proejct maintainer to know. Eventually, Google changed their policy to no longer recommend trying to keep the AUTHORS file up to date proactively, and instead to only add to it when requested: https://opensource.google/docs/releasing/authors. They are also clear that: > Adding contributors to the AUTHORS file is entirely within the > project's discretion and has no implications for copyright ownership. It was primarily added to appease a small number of large contributors that insisted that they be recognized as copyright holders (which was entirely their right to do). But it's not truly necessary, and not even the most accurate way of identifying contributors and/or copyright holders. In practice, we've never added anyone to our AUTHORS file. It only lists Tailscale, so it's not really serving any purpose. It also causes confusion because Tailscalars put the "Tailscale Inc & AUTHORS" header in other open source repos which don't actually have an AUTHORS file, so it's ambiguous what that means. Instead, we just acknowledge that the contributors to Tailscale (whoever they are) are copyright holders for their individual contributions. We also have the benefit of using the DCO (developercertificate.org) which provides some additional certification of their right to make the contribution. The source file changes were purely mechanical with: git ls-files | xargs sed -i -e 's/\(Tailscale Inc &\) AUTHORS/\1 contributors/g' Updates #cleanup Change-Id: Ia101a4a3005adb9118051b3416f5a64a4a45987d Signed-off-by: Will Norris <will@tailscale.com>
144 lines
6.0 KiB
YAML
144 lines
6.0 KiB
YAML
# Copyright (c) Tailscale Inc & contributors
|
|
# SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
# Operator oauth credentials. If unset a Secret named operator-oauth must be
|
|
# precreated or oauthSecretVolume needs to be adjusted. This block will be
|
|
# overridden by oauthSecretVolume, if set.
|
|
oauth:
|
|
# The Client ID the operator will authenticate with.
|
|
clientId: ""
|
|
# If set a Kubernetes Secret with the provided value will be created in
|
|
# the operator namespace, and mounted into the operator Pod. Takes precedence
|
|
# over oauth.audience.
|
|
clientSecret: ""
|
|
# The audience for oauth.clientId if using a workload identity federation
|
|
# OAuth client. Mutually exclusive with oauth.clientSecret.
|
|
# See https://tailscale.com/kb/1581/workload-identity-federation.
|
|
audience: ""
|
|
|
|
# URL of the control plane to be used by all resources managed by the operator.
|
|
loginServer: ""
|
|
|
|
# Secret volume.
|
|
# If set it defines the volume the oauth secrets will be mounted from.
|
|
# The volume needs to contain two files named `client_id` and `client_secret`.
|
|
# If unset the volume will reference the Secret named operator-oauth.
|
|
# This block will override the oauth block.
|
|
oauthSecretVolume: {}
|
|
# csi:
|
|
# driver: secrets-store.csi.k8s.io
|
|
# readOnly: true
|
|
# volumeAttributes:
|
|
# secretProviderClass: tailscale-oauth
|
|
#
|
|
## NAME is pre-defined!
|
|
|
|
# installCRDs determines whether tailscale.com CRDs should be installed as part
|
|
# of chart installation. We do not use Helm's CRD installation mechanism as that
|
|
# does not allow for upgrading CRDs.
|
|
# https://helm.sh/docs/chart_best_practices/custom_resource_definitions/
|
|
installCRDs: true
|
|
|
|
operatorConfig:
|
|
# ACL tag that operator will be tagged with. Operator must be made owner of
|
|
# these tags
|
|
# https://tailscale.com/kb/1236/kubernetes-operator/?q=operator#setting-up-the-kubernetes-operator
|
|
# Multiple tags are defined as array items and passed to the operator as a comma-separated string
|
|
defaultTags:
|
|
- "tag:k8s-operator"
|
|
|
|
image:
|
|
# Repository defaults to DockerHub, but images are also synced to ghcr.io/tailscale/k8s-operator.
|
|
repository: tailscale/k8s-operator
|
|
# Digest will be prioritized over tag. If neither are set appVersion will be
|
|
# used.
|
|
tag: ""
|
|
digest: ""
|
|
pullPolicy: Always
|
|
logging: "info" # info, debug, dev
|
|
hostname: "tailscale-operator"
|
|
nodeSelector:
|
|
kubernetes.io/os: linux
|
|
|
|
resources: {}
|
|
|
|
podAnnotations: {}
|
|
podLabels: {}
|
|
|
|
serviceAccountAnnotations: {}
|
|
# eks.amazonaws.com/role-arn: arn:aws:iam::123456789012:role/tailscale-operator-role
|
|
|
|
tolerations: []
|
|
|
|
affinity: {}
|
|
|
|
podSecurityContext: {}
|
|
|
|
securityContext: {}
|
|
|
|
extraEnv: []
|
|
# - name: EXTRA_VAR1
|
|
# value: "value1"
|
|
# - name: EXTRA_VAR2
|
|
# value: "value2"
|
|
|
|
# In the case that you already have a tailscale ingressclass in your cluster (or vcluster), you can disable the creation here
|
|
ingressClass:
|
|
# Allows for customization of the ingress class name used by the operator to identify ingresses to reconcile. This does
|
|
# not allow multiple operator instances to manage different ingresses, but provides an onboarding route for users that
|
|
# may have previously set up ingress classes named "tailscale" prior to using the operator.
|
|
name: "tailscale"
|
|
enabled: true
|
|
|
|
# proxyConfig contains configuraton that will be applied to any ingress/egress
|
|
# proxies created by the operator.
|
|
# https://tailscale.com/kb/1439/kubernetes-operator-cluster-ingress
|
|
# https://tailscale.com/kb/1438/kubernetes-operator-cluster-egress
|
|
# Note that this section contains only a few global configuration options and
|
|
# will not be updated with more configuration options in the future.
|
|
# If you need more configuration options, take a look at ProxyClass:
|
|
# https://tailscale.com/kb/1445/kubernetes-operator-customization#cluster-resource-customization-using-proxyclass-custom-resource
|
|
proxyConfig:
|
|
# Configure the proxy image to use instead of the default tailscale/tailscale:latest.
|
|
# Applying a ProxyClass with `spec.statefulSet.pod.tailscaleContainer.image`
|
|
# set will override any defaults here.
|
|
#
|
|
# Note that ProxyGroups of type "kube-apiserver" use a different default image,
|
|
# tailscale/k8s-proxy:latest, and it is currently only possible to override
|
|
# that image via the same ProxyClass field.
|
|
image:
|
|
# Repository defaults to DockerHub, but images are also synced to ghcr.io/tailscale/tailscale.
|
|
repository: tailscale/tailscale
|
|
# Digest will be prioritized over tag. If neither are set appVersion will be
|
|
# used.
|
|
tag: ""
|
|
digest: ""
|
|
# ACL tag that operator will tag proxies with. Operator must be made owner of
|
|
# these tags
|
|
# https://tailscale.com/kb/1236/kubernetes-operator/?q=operator#setting-up-the-kubernetes-operator
|
|
# Multiple tags can be passed as a comma-separated string i.e 'tag:k8s-proxies,tag:prod'.
|
|
# Note that if you pass multiple tags to this field via `--set` flag to helm upgrade/install commands you must escape the comma (for example, "tag:k8s-proxies\,tag:prod"). See https://github.com/helm/helm/issues/1556
|
|
defaultTags: "tag:k8s"
|
|
firewallMode: auto
|
|
# If defined, this proxy class will be used as the default proxy class for
|
|
# service and ingress resources that do not have a proxy class defined. It
|
|
# does not apply to Connector resources.
|
|
defaultProxyClass: ""
|
|
|
|
# apiServerProxyConfig allows to configure whether the operator should expose
|
|
# Kubernetes API server.
|
|
# https://tailscale.com/kb/1437/kubernetes-operator-api-server-proxy
|
|
apiServerProxyConfig:
|
|
# Set to "true" to create the ClusterRole permissions required for the API
|
|
# server proxy's auth mode. In auth mode, the API server proxy impersonates
|
|
# groups and users based on tailnet ACL grants. Required for ProxyGroups of
|
|
# type "kube-apiserver" running in auth mode.
|
|
allowImpersonation: "false" # "true", "false"
|
|
|
|
# If true or noauth, the operator will run an in-process API server proxy.
|
|
# You can deploy a ProxyGroup of type "kube-apiserver" to run a high
|
|
# availability set of API server proxies instead.
|
|
mode: "false" # "true", "false", "noauth"
|
|
|
|
imagePullSecrets: []
|