<caption><image_218>The image is a screenshot of a webpage with a white background and a blue header. At the top of the page, there is a search bar and a menu bar with various options such as File, Edit, View, Tools, and Help. Below the header, there are two lines of text that reads "Welcome to nginx". The text is in black font and is centered on the page. There is a small black dot in the bottom right corner of the image.</caption><transcript><audio_219>should see the default engine X page so here we started that container configured the routing mesh and we're able to access that new application so it can be as simple as that a lot of automation a lot of process so my developers can go in deploy their own application so it's automatically</transcript><caption><image_220>The image is a screenshot of a computer screen with a white background. At the top of the screen, there is a menu bar with various options such as File, Edit, View, Tools, and Help. Below the menu bar, there are several tabs for different settings and options. On the right side of the image, there appears to be a search bar with a red arrow pointing to the right. In the center of the screenshot, there seems to be an empty space with a small white circle in the middle. The image is taken from a top-down view of the computer screen.</caption><transcript><audio_221>Services then the next thing that I wanted to talk about was world-based access control for secet and volumes so we've extended the RO based access control that exists as the was talking about and that's been extended for secrets so Secrets as we were talking</transcript><transcript><audio_222>about earlier have specific labels that have been defined to determine who actually has access to the secrets so that limits the scope of who has access to a given secret so that for example if I have multiple uh teams that are</transcript><transcript><audio_223>deploying their applications in UCP they can only see the secrets that are specifically defined for them so just to show what happens let's go a and create a new Secret</transcript><transcript><audio_224>and provide some data and in this case let me go ahead and set my staging application so now I've set that access</transcript><transcript><audio_225>label so I now have that new secret with a different access label and that this access control is still done by teams so we can see in my Docker demo team that has been created My Demo 2 user is a member of the this team we see that we have our</transcript> should see the default engine X page so here we started that container configured the routing mesh and we're able to access that new application so it can be as simple as that a lot of automation a lot of process so my developers can go in deploy their own application so it's automatically Services then the next thing that I wanted to talk about was world-based access control for secet and volumes so we've extended the RO based access control that exists as the was talking about and that's been extended for secrets so Secrets as we were talking about earlier have specific labels that have been defined to determine who actually has access to the secrets so that limits the scope of who has access to a given secret so that for example if I have multiple uh teams that are deploying their applications in UCP they can only see the secrets that are specifically defined for them so just to show what happens let's go a and create a new Secret and provide some data and in this case let me go ahead and set my staging application so now I've set that access label so I now have that new secret with a different access label and that this access control is still done by teams so we can see in my Docker demo team that has been created My Demo 2 user is a member of the this team we see that we have our
{"source": "grass-yt-cc-by.180RC4tlwIQ|shard_10008_13|create_multimodal_data.extract_yt_and_generate_transcripts.57|shard_10008|create_multimodal_data.generate_captions.57|shard_10008|create_multimodal_data.generate_captions.57", "params": {"id": "180RC4tlwIQ", "channel_id": "UC76AVf2JkrwjxNKMuPpscHQ", "duration": 3452, "view_count": 1271, "age_limit": 0, "chapters": [{"start_time": 0, "end_time": 99.0, "title": "<Untitled Chapter 1>"}, {"start_time": 99.0, "title": "Docker at the center of enterprise IT transformation", "end_time": 212.0}, {"start_time": 212.0, "title": "Docker Datacenter Integrated Platform", "end_time": 341.0}, {"start_time": 341.0, "title": "Docker Datacenter CaaS Overview", "end_time": 432.0}, {"start_time": 432.0, "title": "What's New in Docker Datacenter on Docker 1.13", "end_time": 628.0}, {"start_time": 628.0, "title": "The Key Components of Container Security", "end_time": 709.0}, {"start_time": 709.0, "title": "Integrated Secrets Management", "end_time": 858.0}, {"start_time": 858.0, "title": "Safer Apps with Docker Security Scanning", "end_time": 976.0}, {"start_time": 976.0, "title": "Improved Access Control", "end_time": 1050.0}, {"start_time": 1050.0, "title": "Compose for Services", "end_time": 1114.0}, {"start_time": 1114.0, "title": "Image Content Cache", "end_time": 1240.0}, {"start_time": 1240.0, "title": "Built in HTTP Routing Mesh (Now GA!)", "end_time": 1374.0}, {"start_time": 1374.0, "title": "Webhooks for Registry Events", "end_time": 1443.0}, {"start_time": 1443.0, "title": "UCP Node Metrics", "end_time": 1492.0}, {"start_time": 1492.0, "title": "Install DTR from the UCP UI", "end_time": 1546.0}, {"start_time": 1546.0, "title": "DDC Templates for AWS and Azure", "end_time": 1595.0}, {"start_time": 1595.0, "title": "Pricing and Packaging Summary", "end_time": 3452}], "like_count": 7, "channel_follower_count": 103000, "license": "Creative Commons Attribution license (reuse allowed)", "uploader_id": "@DockerInc", "yt_tar_file": "/leonardo_work/EUHPC_E03_068/audio/fixed_download/grass-yt-cc-by//shard_10008/180RC4tlwIQ.tar.gz"}}