Remove container runtime interface (CRI) placeholder

Change-Id Ib1dd5bd (stx-puppet) and Icc5fd16 (config) add
support to set CRI entries for kubernetes runTimeClass.

This is not needed during the initial bring-up of services
at bootstrap time and produces incorrect config.toml causing
bootstrap failure. Therefore, it is removed from the initial
config.toml generated during bring up of essential services.

Story: 2008434
Task: 41928

Depends-On: https://review.opendev.org/c/starlingx/config/+/776220
Depends-On: https://review.opendev.org/c/starlingx/stx-puppet/+/776223

Signed-off-by: Babak Sarashki <babak.sarashki@windriver.com>
Change-Id: Id124653329da0ba9f990e5bba6b53faa3c88fa86
This commit is contained in:
Babak Sarashki 2021-02-24 05:45:30 +00:00
parent 3babc1eed3
commit ff5c9327c1

View File

@ -139,6 +139,12 @@
environment:
STREAM_SERVER_ADDRESS: "{{ stream_server_address }}"
- name: Remove custom container runtime CRI entries
command: >-
sed -i -e '/^# MARK_BEGIN_custom_container_runtime/,/^# MARK_END_custom_container_runtime/d' /etc/containerd/config.toml
args:
warn: false
- name: Remove central cloud registry config on non-subclouds
replace:
path: /etc/containerd/config.toml