[Starlingx-discuss] New Kubernetes namespaces introduced by
HI Jerry Why psp-rolebinding helm chart integrated in openstack application. So to create a new k8s namespace, firstly should apply stx-openstack? $ system service-parameter-add kubernetes kube_apiserver admission_plugins=PodSecurityPolicy $ system service-parameter-apply Kubernetes For above two command which parameter is newly created namespace name? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request@lists.starlingx.io <starlingx-discuss-request@lists.starlingx.io> Sent: Friday, July 3, 2020 6:57 AM To: starlingx-discuss@lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 26, Issue 5 Send Starlingx-discuss mailing list submissions to starlingx-discuss@lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request@lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner@lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Sanity Master Test MONOLITHIC build ISO 20200701T054008Z (Jascanu, Nicolae) 2. New Kubernetes namespaces introduced by new applications (Sun, Yicheng (Jerry)) 3. [Diversity] Diversity & Inclusion WG Meeting 7/6 (Amy Marrich) 4. [build-report] STX_BUILD_3.0 - Build # 22 - Failure! (build.starlingx@gmail.com) ---------------------------------------------------------------------- Message: 1 Date: Thu, 2 Jul 2020 16:01:28 +0000 From: "Jascanu, Nicolae" <nicolae.jascanu@intel.com> To: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200701T054008Z Message-ID: <BN8PR11MB361750FDF5BE297184B6625DE36D0@BN8PR11MB3617.namprd11.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Sanity Test from 2020-July-01 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/2... ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/2... A LP was created: https://bugs.launchpad.net/starlingx/+bug/1886003 Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20200702/765afcb5/attachment-0001.html> ------------------------------ Message: 2 Date: Thu, 2 Jul 2020 17:19:55 +0000 From: "Sun, Yicheng (Jerry)" <Jerry.Sun@windriver.com> To: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] New Kubernetes namespaces introduced by new applications Message-ID: <CH2PR11MB43598F19EEE4188AC3215602EB6D0@CH2PR11MB4359.namprd11.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Hi All, If you are introducing a new Kubernetes namespace with a new application, please also deploy the psp-rolebinding helm chart from the helm-charts repo. If this is not deployed, you may encounter deployment issues if the pod security plugin is enabled on the Kubernetes cluster. To test, enable pod security plugin: system service-parameter-add kubernetes kube_apiserver admission_plugins=PodSecurityPolicy system service-parameter-apply Kubernetes and then deploy your application. Example of how to include the psp-rolebinding helm chart in your application: https://opendev.org/starlingx/openstack-armada-app/commit/92ed6fecc714e373b9... https://opendev.org/starlingx/openstack-armada-app/commit/0cdedf8e447f5be0d7... Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20200702/5c24c1a3/attachment-0001.html> ------------------------------ Message: 3 Date: Thu, 2 Jul 2020 16:22:57 -0500 From: Amy Marrich <amy@demarco.com> To: foundation@lists.openstack.org, starlingx-discuss@lists.starlingx.io, airship-discuss@lists.airshipit.org, kata-dev@lists.katacontainers.io, zuul-discuss@lists.zuul-ci.org, openstack-discuss <openstack-discuss@lists.openstack.org> Subject: [Starlingx-discuss] [Diversity] Diversity & Inclusion WG Meeting 7/6 Message-ID: <CAFs83QrKQT08_hhd--1S9EduMCFY38UOWk-srsDmUSqaBJ_esQ@mail.gmail.com> Content-Type: text/plain; charset="utf-8" The Diversity & Inclusion WG invites members of all OSF projects to our next meeting Monday, July 6th, at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity -wg-agenda. We will be discussing changing our Wiki page to reflect the broader OSF projects and communities so that the page reflects our mission. Please feel free to add any other topics you wish to discuss at the meeting. Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20200702/5d6b0943/attachment-0001.html> ------------------------------ Message: 4 Date: Thu, 2 Jul 2020 18:57:20 -0400 (EDT) From: build.starlingx@gmail.com To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_BUILD_3.0 - Build # 22 - Failure! Message-ID: <1295984222.1941.1593730641635.JavaMail.javamailuser@localhost> Content-Type: text/plain; charset="utf-8" Project: STX_BUILD_3.0 Build #: 22 Status: Failure Timestamp: 20200702T223225Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200702T223... -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: true BUILD_CONTAINERS_STABLE: true ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 26, Issue 5 ************************************************
participants (1)
-
Chen, Haochuan Z