You do not have permission to edit this page, for the following reasons:

The action you have requested is limited to users in one of the groups: Users, static, property, Wikiteam, Formeditor, Sessioneditor, Roomeditor.
The action you have requested is limited to users in one of the groups: Administrators, emailconfirmed, Sessioneditor.

Please read before you start to fill in the form!

Do not use square-brackets ( "[" or "]" ) within the form fields, as this will mess up the wiki page you are editing
Do not use the pipe symbol ( "|" ) within any form fields
There is one exception for the rules above. You can use the stated characters within the free text field at the end of the page

To register a session, you need to have a validated e-mail address in your account settings.

Basic description[edit]

Please enter a basic description for the planned Self-Organized Session. For more information about Self-Organized Sessions head to Self-Organized Sessions.

Tags
	Add tags describing your session. You might want to use tags provided via autocompletion or add new tags that do not yet exist in the wiki.

Kids session	is a kids session.
	Check this box if the workshop is meant for kids rather than grownups.

Short description
	Enter a short basic description for the Self-Organized Session. Do not use wikicode here except linebreaks and lists. For a full description, use the Free Text field.

Website
	If the Self-Organized Session has a website with additional information you like to provide, add it here. You can add multiple websites separated by comma (",").

Type
	Select the type of your Self-Organized Session from the list. This will be used for categorizing the Self-Organized Sessions within the calendar.

Keywords
	Select some keywords that might fit your Self-Organized Session's intents.

Assembly
	Select an Assembly processing this Self-Organized Session. This field provides autocompletion.

Organizing person
	Add the person organizing the Self-Organized Session. As you are just creating it, you should probably be the one here. This field only accepts registered users who created a userpage from this wiki. You can add multiple values separated by comma (","). If you don't find yourself in this list, create a userpage first by using the form provided.

Languages
	Select the language one should speak to attend the Self-Organized Session.

Orga contact
	Give us organizational contact information for further questions. This has to be a valid e-mail address.

Related project
	If this Self-Organized Session is related to a project presented on the 36C3, you can enter the name here to link it to the project page. This field allows only existing Static:Projects.

Timeslots[edit]

Add times where you like to run your activities here by just pressing "Add another…". You can add multiple times if you like to split your event over multiple timeslots. A Self-Organized Session should have at least one timeslot though ;)

Optional subtitle
	Add an optional subtitle here. The subtitle might be interesting if you have a Self-Organized Session that consists of multiple parts. For example: Introduction, Hands-On

Start time
	Format: YYYY/MM/DD hh:mm – Provide a start time so participants know when they should show up. Day 1: 27th, Day 2: 28th, Day 2: 29th, Day 4: 30th Please check if the timeslot is still available!!!!111 (You can use the Timetable.)

Duration in minutes
	Provide the duration of the event in minutes so participants know how long it will take.

Location
	Select a location where the Self-Organized Session should take place within this timeslot. The list contains official workshop locations as well as Assemblies that provide space for workshops. If you like to perform a workshop at an Assembly you are not a member of, please ask the members if it is ok in advance. If you want to use one of the assembly stages please get in touch with them before you enter your session on their stage.

Free text[edit]

Enter a full description of the event here. The field allows using the full mediawiki syntax for text formating.

The organizer has audited and consulted on several projects of Kubernetes in critical infrastructure. Areas audited are traffic control, power grids and several health care projects. Some show very strict awareness of security, others have approached the topic totally naive. Let us exchange ideas about the bare necessities and no gos for microservices going critical.

Summary:

This is a minor edit Watch this page

Cancel

Edit Session: Session:Kritical - Kubernetes in Critigal Infrastructure

Basic description[edit]

Timeslots[edit]

Free text[edit]