NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #734 by repository stars
Last release 7 years ago
no release in 18 months
Ships fairly regularly
a new release about every 3 weeks
Some releases are documented
notes for 3 of 10 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
20 releases · first in 2018
- #1099 Updates to propagation status are now only made in response to propagation to member clusters or errors in propagation. Previously propagation
/spec/replicas. Previously the controller was able
to create and remove overrides for the replicas field but would
fail to update them.kubefedctl commands now default --host-cluster-context to the
current context in log messages.kubefedctl federate now removes all metadata fields except labels
from the template of federated resources created from a
non-federated resource. Previously metadata.annotations and
metadata.finalizers were not removed which could result in
propagation errors.One column per quarter.
- #1058 KubeFedConfig spec.scope is now immutable. - #1052 Support has been added for varying the apiVersion of target resources. This is intended to
apiVersion of target
resources. This is intended to allow a federated type to manage
more than one version of the target type across member clusters.
apiVersion can be set either in the template of a federated
resource or via override.- #908 Adds admission webhook validations for KubeFedCluster API. - #982 To ensure compatibility with controllers in member clusters, metadata.finaliz
kubefedctl
by adding the orphaning-deletion command, which allows to enable or disable
leaving managed resources, when their relevant federated resource is deleted.
In addition, the command allows to check current status of the orphaning deletion
mode.federate and all orphaning-deletion commands is not specified, use the namespace from
the client kubeconfig context.- #520 Adds support for jsonpath overrides. - #965 Adds admission webhook support for namespace-scoped deployments. - #941 Adds admission webhook vali
Nothing published for this version
API group changed from federation.k8s.io to kubefed.k8s.io
kubefedctl federate can take input from a file via --filename
option and stdin via --filename - option.federation-system to kube-federation-system. The kube-
prefix is reserved for system namespaces and including it avoids
having the kubefed namespace conflict with a user namespace.kubefedctl federate namespace with its content gets an option to
skip API Resources via --skip-api-resources.- #722 - Removal of the FederatedTypeConfig for namespaces now disables all namespaced sync controllers. Additionally, the namespace FederatedTypeConf
kubefedctl federate ns <namespace> --contents.- #776 - Switch to use scope instead of limitedScope to specify if it is Namespaced or Cluster scoped federation deployment. - #797 - Cross-cluster se
scope instead of limitedScope to specify if it is
Namespaced or Cluster scoped federation deployment.kubefed2 enable now succeeds if federation of the type is already
enabled.kubefed2 enable required arguments and remove unnecessary
--registry-namespace option from kubefed2 <enable|disable>.kubefed2 federate now supports the --enable-type flag to optionally
enable the given type for propagation.Removed generated typed clients for federation apis from tree. Use generic client to operate on federation apis as shown here
kubefed.k8s.io/sync-controller instead of
federation.kubernetes.io/delete-from-underlying-clusters) and
replaced the use of the kube orphan finalizer in favor of an
annotation to avoid conflicting with the garbage collector. This
change in finalizer usage represents a breaking change since
resources reconciled by previous versions of the sync controller
will have the old finalizer. The old finalizer would need to be
manually removed from a resource for that resource to be garbage
collected after deletion.retainReplicas of type boolean rather than the invalid type
bool.kubefed2 federate has been updated to support output to yaml via
-o yaml. YAML output would still require a Kubernetes API endpoint
to function.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →