Releases: jthomperoo/custom-pod-autoscaler-operator
Releases · jthomperoo/custom-pod-autoscaler-operator
v1.0.1
[v1.0.1] - 2020-08-15
Fixed
- When deploying using Cluster wide scope to a namespace, the
ClusterRoleBinding
no longer only searches in thedefault
namespace for the
ServiceAccount
- instead it searches in the namespace that the helm chart is
deployed to. This change is only for the helm deploys, as such the kubectl
deployment method is no longer recommended, as it only supports deploying to
thedefault
namespace for cluster wide installs.
v1.0.0
[v1.0.0] - 2020-07-19
v0.7.0
[v0.7.0] - 2020-07-18
Changed
- CustomPodAutoscaler resource changed from
v1alpha
tov1
. - Operator Docker image now using
distroless
rather than RHELubi7
. - Add deployment via helm.
v0.6.0
Added
- New options for deciding if a resource should be provisioned by the CPAO, or if they
are provided already by the user/another system. All provision options default to
true
.provisionRole
- determines if aRole
should be provisioned.provisionRoleBinding
- determines if aRoleBinding
should be provisioned.provisionServiceAccount
- determines if aServiceAccount
should be
provisioned.provisionPod
- determines if aPod
should be provisioned.
- Resources can now be updated at runtime, without deleting and recreating the CPA.
- All resources will be updated using the standard K8s Update procedure, except
forPod
resources, which will be deleted and recreated, in order to use any
new image provided.
- All resources will be updated using the standard K8s Update procedure, except
v0.5.0
[v0.5.0] - 2020-01-18
Added
- Add permissions to role for managing ReplicationControllers, ReplicaSets, and StatefulSets.
- Add permissions to use scaling API.
- When a resource already exists, the operator will check if the assigned CPA has been set as its owner; if it isn't it will set it, if not it will skip it. This can be used by CPAs to modify the resources for the CPA.
0.4.0
Update CI to parse version at release (#46)
0.3.0
Cut 0.3.0 release (#32)
0.2.1
Cut version 0.2.1 (#29)
0.2.0
Cut 0.2.0 release (#26)
0.1.0
Add publish deploy YAML to releases (#10)