Skip to content

Releases: openshift/sandboxed-containers-operator

v1.5.2

07 Feb 17:00
@gkurz gkurz
v1.5.2
b8b3307
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.5.2

What's Changed

New Contributors

Full Changelog: v1.5.1...v1.5.2

Contributors

gkurz, tbuskey, and snir911
Assets 2
Loading

v1.5.1

02 Feb 14:17
@gkurz gkurz
v1.5.1
817ff2a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.5.1

What's Changed

Full Changelog: v1.5.0...v1.5.1

Contributors

gkurz and snir911
Assets 2
Loading

sandboxed containers operator v1.5.0

23 Nov 14:55
@gkurz gkurz
v1.5.0
9891e9b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
sandboxed containers operator v1.5.0

What's Changed

  • Fast-forward devel to peer-pods-tech-preview by @pmores in #315
  • Merge main into devel after v1.4.0 release by @gkurz in #325
  • image-job: fix payload url by @snir911 in #324
  • Allow monitor pods to run on tainted nodes by @gkurz in #328
  • Fix kataconfig status handling to support installation updates by @pmores in #327
  • New way of showing kata nodes in kataconfig status by @pmores in #329
  • Switch to condition for progress status reporting by @pmores in #330
  • Bump outdated versions of OSC components by @gkurz in #332
  • Update machineconfig to enable required annotations for flexible instance types by @bpradipt in #335
  • Add snir911 to reviewers and approvers by @jensfr in #334
  • Remove legacy kata config status parts by @pmores in #333
  • Fix kataconfig status handling to support installation updates (port to main) by @gkurz in #339
  • Use raw Azure base image for peer-pods by @bpradipt in #340
  • Support multiple runtimeclasses in kataconfig.status.runtimeClass by @pmores in #344
  • PR #344 fixup by @pmores in #345
  • Update peerpodconfig-ctl dep by @bpradipt in #342
  • Peer-pods: switch runtime class name to 'kata-remote' instead of 'kata… by @littlejawa in #346
  • podvm: run image jobs from the controller automatically by @snir911 in #343
  • don't let KataConfig deletion start while installation is still in progress by @pmores in #349
  • peer-pods: validate CM and Secret are set by @snir911 in #353
  • Bump OSC to 1.5.0 by @gkurz in #355
  • Merge to main for 1.5 by @gkurz in #357
  • peerpod-ctrl: bump to fix dangling VMs by @snir911 in #360
  • makefile: match operator, bundle and catalog versioning by @snir911 in #361
  • image-generator: skip image creation for unsupported providers by @snir911 in #362
  • Merge to main for 1.5 by @gkurz in #363

Full Changelog: v1.4.1...v1.5.0

Contributors

jensfr, littlejawa, and 4 other contributors
Assets 2
Loading

sandboxed containers operator v1.4.1

17 Nov 07:22
@gkurz gkurz
v1.4.1
1a660d8
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
sandboxed containers operator v1.4.1

What's Changed

Full Changelog: v1.4.0...v1.4.1

Contributors

gkurz
Assets 2
Loading

sandboxed containers operator v1.4.0

09 Jun 16:28
@gkurz gkurz
v1.4.0
d255dac
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
sandboxed containers operator v1.4.0

Highlights

  • Peer Pods : use an remote hypervisor (AWS or Azure) to run the kata VMs
  • Massive improvements in the installation/uninstallation logic of the KataConfig CR

What's Changed

New Contributors

Full Changelog: v1.3.3...v1.4.0

Contributors

beraldoleal, jensfr, and 9 other contributors
Assets 2
Loading

sandboxed containers operator v1.3.3

30 Jan 16:19
@jensfr jensfr
v1.3.3
0c03c3a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
sandboxed containers operator v1.3.3

What's Changed

  • Update version and change default channel by @jensfr in #256

Full Changelog: v1.3.2...v1.3.3

Contributors

jensfr
Assets 2
Loading

sandboxed containers operator v1.3.2

18 Jan 15:46
@jensfr jensfr
v1.3.2
ef92c21
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
sandboxed containers operator v1.3.2

Changelog

v1.3.2 (2023-01-18)

Full Changelog

Closed issues:

  • Update to golang 1.18 #214
  • add .dockerignore from operator-sdk #212
  • Modified files after building #209
  • Add build artifacts to .gitignore #208
  • DEVELOPMENT.md is out of date and does not work #207
  • Basic CI for PR checks #206
  • run 'make test' during pre-merge test #174
  • error 'failed to check Node eligibility' when running make test #173
  • status not updated when nodes are added/removed from machine config pool #170
  • release-1.1: deployment breaks due to flag provided but not defined: -metrics-addr #159
  • release-1.1 deployment instructions is pointing to wrong links #158
  • Create and publish a release-4.9 branch #157
  • README from master doesn't point to 4.8 nor 4.9 README #156
  • Add Dockerfile and related artefacts for kata-monitor #150
  • Deployment instructions are missing #139
  • fix retrieving list of nodes #135
  • Cannot install 1.1.0 operator in OCP 4.9 #133
  • add more operator debug data to must-gather image #129
  • Removed unused code #121
  • NodeSelector is not being set for RuntimeClass when using MatchExpressions in KataConfigPoolSelector #118
  • [Question] What steps can I take to manually verify that the kata runtime is indeed being used by the example workload provided? #115
  • Kata deployment stalls with invalid extensions error #113
  • [RFE] Get rid of sleeps in our codebase #87
  • [RFE] Support sandboxed-containers-operator as part of OKD #86
  • followed "without a git repo checkout" steps, failed to launch qemu #65
  • Limit the installation to known and tested cases #60
  • installation stuck when selected node is in custo machine-config pool #56
  • cordoned workers are ignored, installation won't finish #52
  • daemon: "E1123 Unable to rotate token " #33

Merged pull requests:

Read more
Assets 2
Loading

1.0.0

03 Aug 14:14
@jensfr jensfr
v1.0.0
e7a7ca7
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
1.0.0

Release notes for 1.0.0

Highlights

  • rename kata-operator to sandboxed-containers-operator
  • the payload and daemonset have been removed and replaced by sandboxed-containers RHCOS extension.

Tested features

  • enabling and disabling the sandboxed-containers RHCOS extension
  • installation of Kata with the operator
  • deploy of a pod using the Kata runtime
  • deletion of pod that uses the Kata runtime
  • uninstall of Kata with the operator

Tested configurations

  • Openshift on 4.8 on Google Cloud Platform, 3 masters/3workers, 3 nodes master/worker combined
  • Openshift on 4.8 in a disconnected cluster

Note: Installing on other cloud infrastructures or single bare metal machines should work as long as nested VMs are enabled

Known issues:

  • Benign errors in kata-operator logs https://bugzilla.redhat.com/show_bug.cgi?id=1890509
  • you cannot use the hostPath volume in a OpenShift Container Platform cluster to mount a file or directory from the host node’s file system into your pod. (BZ#1904609)
  • If you are running Fedora on OpenShift sandboxed containers, you need a workaround to install some packages. Some packages, like iputils, require file access permission changes that OpenShift Container Platform does not grant to containers by default. To run containers that require such special permissions, it is necessary to add an annotation to the YAML file describing the workload, which tells virtiofsd to accept such file permissions for that workload. The required annotations are: io.katacontainers.config.hypervisor.virtio_fs_extra_args: [ "-o", "modcaps=+sys_admin", "-o", "xattr" ] BZ#1915377
  • In the 4.8 release, adding a value to kataConfgPoolSelector by using the OpenShift Container Platform web console causes scheduling.nodeSelector to be populated with an empty value. Pods that use RuntimeClass with the value of kata might be scheduled to nodes that do not have the Kata Containers runtime installed.
    To work around this issue, specify the nodeSelector value manually in the RuntimeClass kata by running the following command:
    $ oc edit runtimeclass kata
    The following is an example of a RuntimeClass with the correct nodeSelector statement.
handler: kata
kind: RuntimeClass
metadata:
  creationTimestamp: "2021-06-14T12:54:19Z"
  name: kata
overhead:
  podFixed:
    cpu: 250m
    memory: 350Mi
scheduling:
  nodeSelector:
    custom-kata-pool: "true"

KATA-764

  • The OpenShift sandboxed containers Operator details page on Operator Hub contains a few missing fields. The missing fields do not prevent you from installing the OpenShift sandboxed containers Operator in 4.8. KATA-826
  • Creating multiple KataConfig custom resources results in a silent failure. The OpenShift Container Platform web console does not provide a prompt to notify the user that creating more than one custom resource has failed. KATA-725
  • Sometimes the Operator Hub in the OpenShift Container Platform web console does not display icons for an Operator. KATA-804
Assets 2
Loading

4.7

12 Feb 20:04
@jensfr jensfr
v4.7
b6343f4
Compare
Choose a tag to compare
4.7

Release notes for 4.7:

Highlights

  • upgraded operator to Operator SDK v1.0
  • support for custom payload images (dev and test only feature)
  • Bugfix "increase memory limits and requests for manager container", PR #42
  • use digests instead of tags for container images to allow offline use of the operator

Tested features

  • Installation of Kata with the operator
  • Deploy of a pod using the Kata runtime
  • Deletion of pod that uses the Kata runtime
  • Uninstall of Kata with the operator

Tested configurations

  • Openshift on 4.7 on Google Cloud Platform, 3 masters/3workers, 3 nodes master/worker combined
  • Openshift on 4.7 in a disconnected cluster

Note:Installing on other infrastructures or baremetal should work as long as nested VMs are enabled

Known issues:

Full list of changes

v4.7 (02/12/2021)

Assets 2
Loading

4.6

23 Oct 14:41
@jensfr jensfr
v4.6
723d90e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
4.6

Installation

The release-4.6 branch README.md contains instructions specific to this release.
https://github.com/openshift/kata-operator/blob/release-4.6/README.md

Tested Features

  • Installation of Kata with the operator
  • Deploy of a pod using the Kata runtime
  • Deletion of pod that uses the Kata runtime
  • Uninstall of Kata with the operator

Tested configurations

Openshift on 4.6 on Google Cloud Platform

Note:Installing on other infrastructures or baremetal should work as long as nested VMs are enabled

Known issues

Benign errors in kata-operator logs
https://bugzilla.redhat.com/show_bug.cgi?id=1890509

Assets 2
Loading