← Back to Blog

Come back to the game ( OS Part 3.1 )

Come back to the game ( OS Part 3.1 ) Kubernetes is asked ! Get the host machine and setup the openshift> video production to move in the back slowly is ok learn from the process. Get your linux box ready in the cloud with IAC.

Come back to the game ( OS Part 3.1 )

Kubernetes is asked !

Get the host machine and setup the openshift> video production to move in the back slowly is ok learn from the process.

Get your linux box ready in the cloud with IAC.

90 minutes to install the UI to ubunut 24 is not acceptable > find the image for the host!

practical screenshots

come back to 1

Part 2> https://wordpress.com/post/rifaterdemsahin.com/29268

Part 1 > https://rifaterdemsahin.com/2024/03/04/openshift-course-pluralsight/

come back to 2

I admit to run simple process you need the K8s and the ASE and appservices has shortcomings more automated approach with the release train engine as k8s.

Interviews reflect it

02:58 I'll do hello. This is Rufat speaking I'm fine. How do you do **xxx**? Yes, it's a perfect time to speak I'm going to go back in, but I'm going to go think about what kind of you'll collaborate with the situation. 07:01 I have my own company in United Kingdom for the last seven years. I was thinking contracting for the enterprise customers such as Goldman Sachs was one of my customers. 07:15 The time I was working for American-based finance company. What I do is dev AI ops, while the AI is getting more and more prevalent in the industry. 07:28 I started implementing the AI practices in the DevOps space calling the AI ops and approaching the customers for the transformation. 07:41 So I was being contacting by Goldman Sachs all over the globe. I work with different contracts, including the one in Switzerland, one in Canada. 07:54 I did work multiple contracts in United Kingdom, and multiple ones in the UAE, in the Gulf area. So, you working in the United States? 08:07 Yes, I got my indefinitely to remain, and I had not contracts at the moment, so I started looking for the market. 08:15 and for the opportunities, and I think I did look at the **xxx**. I'm using the Starlink very similar, I suppose, in different places probably, but the new modern banks, I'm very interested on them, and very close to London. 08:33 I did work in four or five different finance projects in London. I live in Cambridge, but I did contract through all over the globe. 08:42 And what I realize is your time zone was coming from Musket, from Oman. So I did have contracts in Oman as well. 08:54 Okay, so that means, would you be able to go from London to Bangkok with physician? Yes, definitely. London is fortunate. 09:01 That's a way from me. And I will be able to do a hybrid position. Are we talking about a contract? 09:08 Or for a permeable opportunity? Yes, because I got the indefinite literature main, right now I started opening myself up to parliament roles because seven years ago I was working in Microsoft as a permanent employee but once I decided to immigrate I had to adapt for my family so I started looking for 09:39 productivity share. Right now the UK market is has ups and downs I guess we are in the downturn so I'm very flexible in terms of the seller requirements. 09:53 Yeah and we're looking face between 75,000 and 85,000 so where would you be on that and where would you be on that I think that will definitely suit me though. 10:06 I'm not looking for the high-end contracts. I understand that it is time to adapt right now and I will definitely go for those numbers. 10:18 Yes. Yes. And the team itself essentially gave the character all of the infrastructure, how to back-end code, etc. And everybody can still have the ability to create the code to pull in, and quickly impossible. 10:37 And they all so look at the kind of all the back-end route, kind of infrastructure for the apps that we use because obviously we're a fully digital And so this role would be more of a deal with **Kubernetes **with the native **aws**. 10:55 And that, essentially, is kind of the main kind of, what I said, language that they use. So, I mean, you're happy that you're comfortable with the **aws** in **Kubernetes**. 11:10 Yes, I delivered more than five plus contracts on **Kubernetes**, and more than 10 plus in **aws** and I'm a regular user for AWS so I will be I would like to work in that kind of an environment and I did projects of **automating infrastructure as code **to accelerate companies for their this new version of infrastructure 11:36 their things gets automated for the stakeholders. I made up some good sense in terms of the selection process, it can be changed to the selection process. 11:47 And the first thing I'll be with is, I'm going to ahead with these, I'll plot fully TV or direct line manager. 12:21 Yes, I guess so. Sorry. I don't know what's happening with my technology today, but everything is going wrong. So I'm sorry. 12:28 So I was saying, yes, it's a two-state process. First aid will be the **xxx**. He's the part of the lead. 12:36 He's your direct line manager, and xxx, who is the he's a senior cloud engineer as well. So he'd be your pair. 12:44 They will ask you, you know, about your hands on experience with Cuban athletes in AWS, my work with it previously. 12:50 And then second aid will be with xxxx, so they're kind of senior management within the engineer of 18. 12:57 and they were, too, almost a bit of a case study with you where they'll kind of, give you some information and you kind of work with them to form a solution. 13:06 So it's not, it's not kind of a yes or no answer. It's more about how you figure out the working and how you get there in every day. 13:16 So I mean, based on all of those sessions will be over teams. The wider team that you'd be working with So you've got Scott and Rob, and then we've got consultant that we use from time to time on kind of an ad top basis. 13:36 So there's the three of you, and then we have two junior platform engineers. So it's kind of a pretty small team, but we cover quite a lot of the business in total is kind of 500 employees or an X. 13:50 All right. Are you happy for me to put QN for interview for the position? Yes, definitely. So they've got availability, they could do tomorrow, between 12 and 12 and 12. 14:03 And yes, we either work 12 or 1 or the worst, they've got availability on Monday. I think the tomorrow sounds good though. 14:12 Let me check my calendar if I have anything tomorrow, but I don't think I have anything tomorrow, but from time to time my life has the kids activities. 14:23 So tomorrow, a 2 p.m. sounds great. So 12 o'clock or one o'clock. One o'clock, tomorrow, one o'clock sounds great. Okay, so what I'll do is after this call, I'll send you the interview invite. 14:41 So we'll have to scroll and remove the email addresses. If you want to look them up on LinkedIn and do it. 14:47 And they'll just be asking about kind of your hands on Kubernetes experience. and where you used it previously in everything. 14:53 And you can use obviously use the opportunity to ask them plenty of questions about the role because it's literally you kind of decided where the right of the opportunity for you and everything. 15:05 So I mean, do you have any questions based on what I've said? Do you kind of need anything from me at this stage? 15:13 No, as far as I understood, this is a Kubernetes and AWS focus control where I will be working in a three-people team. 15:20 And you are going to send me invite for the tomorrow 1pm meeting. Exactly. So the team size, you've got three seniors in the team. 15:32 So you need to be one of the seniors. And one of those people is also a consultant. And then you've got two junior people as well. 15:39 All right. That sounds good. Thanks. I'll send the invite for tomorrow at 1 o'clock. And just give me a few minutes after this call to sort out. 15:47 And if you think of anything in the meantime, just feel free to give me a call back on and either one of the numbers I'll go to from today. 15:55 All right, that sounds very good. Thank you very much. I will record this number and link with zero one as xxx from xxx. 16:04 So I will make sure that I have your phone number recorded on my head. Perfect. Well, really, really good to speak. 16:10 Did you stay with us? Thank you for putting up with my technology issues. And I hope that goes well tomorrow. 16:15 All right. Take care of my set cheers. Take care then bye. Bye.


Get the host working consistently not in 90 minuts

come back to 3

start empty

come back to 4

come back to 5

RHCOS, or Red Hat CoreOS, is a minimal operating system designed for running containerized applications securely and at scale. It's optimized for Kubernetes deployments. When you refer to a "metal image," you're likely talking about a disk image suitable for bare metal installations.

As of my last update, Red Hat provided RHCOS images for various platforms, including bare metal installations. These images could be downloaded from the Red Hat Customer Portal or other official Red Hat sources. However, specific details about the availability or specifications of these images might have changed since then.

If you're looking to obtain an RHCOS metal image for your bare metal deployment, I'd recommend checking the official Red Hat documentation or contacting Red Hat support for the most up-to-date information and resources.

After deployment I have got to manage it as well.

Studio >

come back to 6

Skipping Kubernetes >

come back to 7

Studio and Kubernetes into devops.engineering product

come back to 8

After the client there is the network hassle

come back to 9

Create multiple machines and deploy a webservice code there and change and manage it for devops.engineering show all the life cycle

come back to 10

Create a more generic name

come back to 11

Lock your images and the download cost with complexity

come back to 12

Sbhow case this on devops engineering

come back to 13

Sku error

come back to 14

Look for other images

come back to 15

get them ready

come back to 16

search

`$locName="uksouth"

`

come back to 17

come back to 18

Canonical is a technology company best known for its development and support of the Ubuntu operating system and related projects. Founded in 2004 by South African entrepreneur Mark Shuttleworth, Canonical's mission is to promote and support the open-source software movement.

Ubuntu, one of Canonical's flagship products, is a popular Linux distribution known for its ease of use, regular release cycles, and strong community support. Canonical provides enterprise support services for Ubuntu deployments, including long-term support (LTS) releases tailored for stability and reliability in business environments.

In addition to Ubuntu, Canonical is involved in various other projects and initiatives, such as:

  • Juju: A cloud orchestration tool that facilitates the deployment, management, and scaling of applications in cloud environments.

  • MAAS (Metal as a Service): A tool for provisioning and managing physical servers at scale, particularly in data centers or cloud environments.

  • Snapcraft: A platform for building and distributing software packages, known as snaps, which are designed to work across a wide range of Linux distributions.

  • LXD: A container hypervisor and manager that provides a lightweight alternative to traditional virtualization technologies.

Canonical's contributions to the open-source ecosystem extend beyond individual projects. They actively participate in various upstream communities, contribute code, and collaborate with other organizations to advance the adoption and development of open-source software.

maybe pro is the one i want

come back to 19

It seems like you've listed a set of strings that resemble identifiers or tags. These strings might be related to licensing or subscription codes for Ubuntu Pro, Canonical's premium version of the Ubuntu operating system tailored for enterprise and commercial use.

"0001-com-ubuntu-pro-advanced-sla" suggests a service level agreement (SLA) associated with Ubuntu Pro Advanced support. The additional strings appended to it might represent specific agreements or contracts with different organizations or entities. For instance:

  • "att" could refer to a contract with AT&T.

  • "ca" might denote a contract with a company based in California.

  • "cfx", "csw", "da", "dd", "kudsec", "nestle" could represent contracts with different companies, organizations, or departments.

However, without more context, it's challenging to provide specific information about these identifiers. They likely relate to the commercial agreements or subscriptions for Ubuntu Pro services provided by Canonical. If you're seeking detailed information or assistance related to these identifiers, you may need to reach out to Canonical's sales or support team.

Based on the list provided, "ubuntu" is the identifier that likely corresponds to Ubuntu Desktop. Typically, Ubuntu Desktop editions are identified simply as "ubuntu." Therefore, if you're looking specifically for Ubuntu Desktop, you would use the "ubuntu" identifier.

The other identifiers in the list seem to relate to various versions, distributions, services, and agreements offered by Canonical, but none of them explicitly indicate the Ubuntu Desktop edition.

come back to 20

come back to 21

come back to 22

come back to 23

https://azuremarketplace.microsoft.com/en-us/marketplace/apps/ntegralinc1586961136942.ntg_ubuntu_22_04_daas?tab=overview

come back to 24

come back to 25

come back to 26

come back to 27

come back to 28

come back to 29

they collect your phone

come back to 30

This is the part

come back to 31

"storageProfile": { "osDisk": { "createOption": "fromImage", "managedDisk": { "storageAccountType": "[parameters('osDiskType')]" }, "deleteOption": "[parameters('osDiskDeleteOption')]" }, "imageReference": { "publisher": "ntegralinc1586961136942", "offer": "ntg_ubuntu_22_04_daas", "sku": "ntg_ubuntu_22_04_daas", "version": "latest" } },

come back to 32

Upload ubuntu desktop image to your end

come back to 33

come back to 34

come back to 35

come back to 36

ubuntu conaconial did not load it > https://documentation.ubuntu.com/azure/en/latest/azure-how-to/instances/find-ubuntu-images/

these guys did > https://azuremarketplace.microsoft.com/en-us/marketplace/apps/ntegralinc1586961136942.ntg_ubuntu_22_04_daas?tab=overview

logs in but rdp not on

come back to 37

3 minutes

come back to 38

come back to 39

update needed

come back to 40

delete and redo

come back to 41

Use this reference

"imageReference": { "publisher": "ntegralinc1586961136942", "offer": "ntg_ubuntu_22_04_daas", "sku": "ntg_ubuntu_22_04_daas", "version": "latest" }

After deletion

come back to 42

todo update yopur script instead of installing xrdp install kubernetes tools.

come back to 43

can i use other publishers offers on linux without the cost ?

come back to 44

ask

https://twitter.com/rifaterdemsahin/status/1783422314945638433

Deleting is off now time to go on

come back to 45

Azure response

https://twitter.com/AzureSupport/status/1783422750217974261

Azure not clear on the policy with the offers >

https://learn.microsoft.com/en-us/legal/marketplace/certification-policies

To use your own image reference in an Azure deployment, especially when deploying a virtual machine or service, you need to specify the details of your custom image in the ARM template or through the Azure portal. The snippet you've provided seems to be part of an ARM (Azure Resource Manager) template where you define the properties of the virtual machine you want to deploy.

Here's a step-by-step guide to help you use your own image reference correctly:

  • Ensure the Image is Available: Before deploying, make sure the image is created and stored in Azure. This can be a managed image in your Azure subscription or a shared image from another subscription or Azure Marketplace.

  • Custom Image ID: If you have a custom image (a managed image you created), you should use the resource ID of the image. The resource ID can be found in the Azure portal under the image's properties. It generally looks like this:

/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.Compute/images/{image-name}

  • Modify the ARM Template: Replace the "imageReference" section with your custom image's resource ID. You do this by using the "imageReference" attribute only if you are referencing a Marketplace image as in your example. For a custom image, use the "storageProfile" property:

"storageProfile": {
"imageReference": {
"id": "/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.Compute/images/{image-name}"
}
}

Note that if you're using a Marketplace image, you can specify it as you have, with publisher, offer, SKU, and version.

  • Update Other Parameters: Make sure the other parts of the ARM template, such as VM size, network interfaces, etc., are correctly configured according to your requirements.

  • Deploy the ARM Template: You can deploy the template using Azure CLI, PowerShell, or directly through the Azure portal. Using Azure CLI:

az deployment group create \
--resource-group [Your-Resource-Group] \
--template-file [Path-to-your-template.json] \
--parameters @[Path-to-your-parameters.json]

Using PowerShell:

New-AzResourceGroupDeployment -ResourceGroupName [Your-Resource-Group] -TemplateFile [Path-to-your-template.json] -TemplateParameterFile [Path-to-your-parameters.json]

By following these steps, you can deploy a virtual machine or any other Azure resource using your custom or a specific Marketplace image. If you're new to ARM templates, it might be helpful to experiment in a non-production environment to ensure your configurations are correct.

Creating your own custom virtual machine image in Azure involves capturing a configured VM so that you can redeploy it later or use it as a template for other deployments. Here’s how you can create and manage your own image:

1. Prepare the Virtual Machine

  • Set Up the VM: Start by creating a virtual machine in Azure that meets your requirements. Install any applications, updates, configurations, or files that you want to include in the image.

  • Generalize the VM: Before you capture an image, you must remove machine-specific information from the VM. This process is called "generalizing." If you're using a Windows VM, you can generalize it using Sysprep, and for Linux VMs, you can use the waagent command. For Windows: %windir%\system32\sysprep\sysprep.exe /generalize /oobe /shutdown For Linux: sudo waagent -deprovision+user -force sudo shutdown -h now

2. Capture the Image

  • Deallocate the VM: After the VM has been generalized and shut down, deallocate the VM using Azure CLI or through the Azure portal. az vm deallocate --resource-group myResourceGroup --name myVM

  • Mark the VM as Generalized: This step is crucial for capturing the image. az vm generalize --resource-group myResourceGroup --name myVM

  • Capture the Image: Finally, capture the image to create a reusable image.
    bash az image create --resource-group myResourceGroup --name myImage --source myVM

3. Use the Image for Deployment

Once your image is captured, it's stored as a managed image in your Azure subscription. You can now use this image to create new VMs:

az vm create \
--resource-group myResourceGroup \
--name myNewVM \
--image myImage \
--admin-username azureuser \
--generate-ssh-keys

4. (Optional) Share the Image

If you want to share this image with other subscriptions or even make it publicly available, you can create a Shared Image Gallery. This allows you to manage, share, and globally distribute your custom VM images:

  • Create an Image Gallery: Create a gallery to hold your images.

  • Add Image to Gallery: Add your managed image to the gallery.

  • Create a Version: Define a version of the image within the gallery.

  • Share the Gallery: You can share the gallery across subscriptions or Azure regions.

5. Management and Compliance

  • Update and Maintenance: Periodically update the image with new software, patches, or configurations.

  • Compliance: Ensure your image complies with your organization's security and compliance standards.

By following these steps, you can efficiently manage and deploy your custom VM images across your Azure environment, enabling a more streamlined and consistent setup for various applications.

my action would be

come back to 46

have the opearting system and do it on your end ?

come back to 47

I need to create my own vhd

come back to 48

come back to 49

To obtain the Virtual Hard Disk (VHD) blob path in Azure, you first need to ensure that you have a VHD file stored as a blob in an Azure Storage Account. This VHD can be used as a source for creating images or directly used for creating new virtual machines. Here's a step-by-step guide on how to find or set up a VHD blob path in Azure:

Step 1: Ensure VHD is Stored in Azure Blob Storage

Before accessing the VHD blob path, make sure that your VHD file is uploaded to an Azure Blob Storage container. If you haven't already uploaded the VHD, you can do so using the Azure Portal, Azure PowerShell, or Azure CLI.

Using Azure CLI:

az storage blob upload --account-name --container-name --name .vhd --file /path/to/your/local.vhd --type page

Step 2: Accessing the VHD Blob Path

Once your VHD is stored in Blob Storage, you can retrieve its path. The path generally has the following format:

https://.blob.core.windows.net//.vhd

Using Azure CLI to list blobs:

az storage blob list --account-name --container-name --output table

This command will list all blobs in the specified container and their properties, including their URL.

Step 3: Use the VHD Blob Path

You can use this VHD blob path in several ways:

  • Create a VM Image: You can create a managed image from the VHD to use in creating virtual machines.

  • Direct VM Creation: You can directly create a new VM using the VHD blob path as the OS disk.

Creating a managed image from the VHD using Azure CLI:

az image create --resource-group --name --os-type --source "https://.blob.core.windows.net//.vhd"

Creating a VM directly from the VHD blob path:

az vm create --resource-group --name --attach-os-disk "https://.blob.core.windows.net//.vhd" --os-type

Additional Considerations

  • Ensure the VHD is generalized if it was previously used as a VM's OS disk.

  • The storage account containing the VHD should have the appropriate access policies if you are using it across different Azure services or subscriptions.

By following these steps, you can manage and utilize VHD files stored as blobs in Azure, allowing for versatile VM deployment and management options within your Azure environment.

Do it loacally and push it than ?

Creating a Virtual Hard Disk (VHD) using VMware Workstation for use in Azure involves several key steps. The general process includes setting up a virtual machine, installing the operating system, preparing the VM for Azure, and converting the VMware disk (VMDK) to a VHD format that Azure supports. Here's how you can do it:

Step 1: Create and Configure a VM in VMware Workstation

  • Open VMware Workstation and create a new virtual machine.

  • Select the Installation Media for the operating system you want to install.

  • Configure the VM’s Hardware such as CPUs, memory, and disk size. Make sure the disk format is set to a single file rather than multiple files for easier conversion later.

  • Install the Operating System on the VM as you would on a physical computer.

Step 2: Install VMware Tools

Once the OS is installed, install VMware Tools in the VM. This improves performance and enhances the management of the virtual machine.

  • From the VMware Workstation menu, choose VM > Install VMware Tools, and follow the instructions provided by the installation wizard inside the VM.

Step 3: Generalize the VM (if using Windows)

If you're installing Windows, you'll need to generalize the OS using Sysprep to remove system-specific data, allowing the image to be reused for multiple VM deployments.

  • Run Sysprep with the generalize option:

C:\Windows\System32\Sysprep\sysprep.exe /generalize /oobe /shutdown

Step 4: Convert the VMware Disk (VMDK) to VHD

After preparing your VM, you need to convert the VMware disk format (VMDK) to a VHD format that Azure can use. This can be done using Microsoft’s free tool called MVMC (Microsoft Virtual Machine Converter) or a third-party tool like StarWind V2V Converter.

  • Using Microsoft Virtual Machine Converter (MVMC):

  • Download and install MVMC.

  • Run the tool and choose to convert the disk.

  • Select the source VMDK file and set the destination format to VHD.

  • Choose whether you want a dynamically expanding or fixed size disk.

  • Using StarWind V2V Converter:

  • Download and install StarWind V2V Converter.

  • Run the converter, select the source VMDK file, and follow the prompts to convert it to VHD format.

Step 5: Upload the VHD to Azure

After converting the disk to VHD, upload it to a blob storage in your Azure subscription.

  • Create a Blob Storage Account in Azure if you don’t already have one.

  • Create a Container in your storage account.

  • Upload the VHD using Azure Storage Explorer or Azure CLI:

az storage blob upload --account-name --container-name --name .vhd --file /path/to/your/local.vhd --type page

Step 6: Create a VM in Azure Using the Uploaded VHD

Now that your VHD is in Azure Blob Storage, you can create a VM in Azure using this VHD as the OS disk.

  • Create a VM with Azure CLI or through the Azure Portal using the VHD as the source for the OS disk.

By following these steps, you can successfully create a VHD in VMware Workstation, convert it for Azure compatibility, and deploy it as a virtual machine in Azure.

heck the cost of the machine

Cost

come back to 50

I can use their image for 6 pounds till i create my own images

To convert the cost from £0.009 per hour to a monthly cost, we'll assume a typical month has about 730 hours (which is 24 hours per day times 30.5 days on average).

Let's calculate:

[ \text{Monthly Cost} = £0.009 \times 730 \text{ hours} ]

[ \text{Monthly Cost} = £6.57 ]

So, the cost per month would be approximately £6.57.

come back to 51

Maybe i generalize that machine....if that works.!

so use it for now

come back to 52

Before

come back to 53

After

come back to 54

With this sku i should update the script to reflect no xrdp installs

my own naming is in

come back to 55

but it is in failed state

come back to 56

source is correct

come back to 57

come back to 58

They make you add to your template the things that they would like to have

It seems you're encountering an error related to deploying a virtual machine (VM) in Microsoft Azure that requires specifying a plan because the VM is based on a Marketplace image or a custom image sourced from a Marketplace image. The error message indicates that the request to create a VM did not include the necessary plan information.

Here's how to resolve this issue:

1. Understand Plan Information

When you deploy a VM from certain Marketplace images, Azure requires you to include plan information in your deployment request. This plan typically consists of the name, product, publisher, and sometimes promotionCode of the image. This information corresponds to the billing and usage terms that were agreed upon when the image was created.

2. Get the Plan Information

You can find the plan information required by following these steps:

  • Go to the Azure Portal.

  • Navigate to the "Virtual Machines" section and try to initiate the creation of a VM.

  • Select the Marketplace image you used for your VM.

  • Just before you finalize the VM creation, Azure will show you the plan details needed for that particular image. Make note of these details.

3. Update Your Deployment Template

If you are using an ARM template or a similar infrastructure-as-code tool, you'll need to include the plan details in your template. Here is an example snippet to include in your ARM template:

"plan": {
"name": "planName",
"publisher": "publisherName",
"product": "productName"
}

Replace "planName", "publisherName", and "productName" with the actual values for the image you are using.

4. Deploy Using Updated Template

After updating your deployment template with the necessary plan information, redeploy your VM. This should resolve the error as Azure now has all the required details to align the deployment with the licensing and billing terms of the image.

5. Learn More

Azure provides documentation on how to handle these types of errors. You can find more detailed guidance by searching "Azure VM deployment plan information required" in the Azure documentation or by visiting the Azure Virtual Machines documentation directly.

If you encounter any further issues, checking the exact error message and consulting Azure's support or documentation for error-specific guidance can also be very helpful.

retrigger the delete

come back to 59

Meet in the middle have the desktop for visualisation on your end and remove the it from the xrpd action.

Set up the linux box naturally > on barebones! and learn in the hassle

bRING ALL THE GUNS

come back to 60

come back to 61

come back to 62

come back to 63

come back to 64

come back to 65

come back to 66

come back to 67

come back to 68

come back to 69

come back to 70

come back to 71

Small mini updates in the back

come back to 72

black screen

come back to 73

not enough ram move to 16

come back to 74

come back to 75

come back to 76

16 gb it turns on

come back to 77

so gpt and wmware workstation helps and you setup the kubernetes host the correct way

come back to 78

come back to 79

come back to 80

London Select

come back to 81

come back to 82

Iso installs are too long! >>> hardware mistach is too much time

come back to 83

it is a gen 1 box

come back to 84

Dopamine > go to omad > and only do with the oxytoxin > hero father

just xclip

come back to 85

come back to 86

update to xclipsetup

come back to 87

sas 2044

come back to 88

come back to 89

come back to 90

Delete the old resource

come back to 91

Lets see how long does it take this time

come back to 92

need to see the input

come back to 93

I pivoted from the openshift trianing of creating the visual one in the cloud to the local

new script worked lets test it

come back to 94

speed is one minute that is great

and i have my ubunutu here to test visually as well

come back to 95

log is there

come back to 96

To use cat in combination with xclip for copying file contents to your clipboard on a Linux system, follow these steps:

  • Ensure xclip is Installed: First, make sure you have xclip installed. You can install it using your package manager. For example, on Ubuntu, you can install it by running:

sudo apt install xclip

  • Using cat and xclip Together:

  • If you want to copy the contents of a file to your clipboard, you can use cat to display the file and pipe it to xclip. For example, to copy the contents of file.txt to the clipboard, you can use:
    bash cat file.txt | xclip -selection clipboard

  • The -selection clipboard option makes sure that the content goes to the clipboard that interacts with Ctrl+C/Ctrl+V operations.

  • Pasting from Clipboard:

  • After you have copied the contents to the clipboard, you can paste them in any application using the standard paste shortcut (usually Ctrl+V).

  • Alternative Usage:

  • If you want to copy the output of any command (not just files) to the clipboard, you can pipe it directly to xclip. For example:
    bash ls -l | xclip -selection clipboard

This method is particularly useful for copying data directly from the terminal to other applications without having to manually select and copy text.

The error "Can't open display: (null)" typically indicates that the xclip command is unable to access the X server, which is necessary for interacting with the clipboard. This issue is common when you are operating in a command-line environment without a graphical interface, such as when connected via SSH or when using a terminal on a server without a desktop environment.

Here are a few solutions you can try to resolve this issue:

1. Specify the Display

If you're running the command in an environment where a graphical interface exists, but xclip doesn't automatically find it, you can explicitly specify the display by setting the DISPLAY environment variable:

DISPLAY=:0 cat /var/log/reboot.log | xclip -selection clipboard

This command assumes that your graphical interface is running on DISPLAY :0, which is common but may vary depending on your setup.

2. Use SSH with X11 Forwarding

If you're connecting to the machine via SSH, you can use X11 forwarding to allow xclip to interact with your local X server. To do this, connect with the -X option:

ssh -X username@hostname

Then run your xclip command:

cat /var/log/reboot.log | xclip -selection clipboard

Ensure that your SSH server and client are configured to allow X11 forwarding. On the server, the X11Forwarding option in /etc/ssh/sshd_config should be set to yes.

3. Alternative Clipboard Utilities

If you are in a non-graphical environment or cannot use X11 forwarding, consider using a different clipboard utility that might not require X11, or you might need to find another method to transfer your data, such as using scp or rsync to copy files directly to a different machine where you can access the contents more easily.

4. Debugging Further

If none of these options are viable or successful, you may need to provide more information about your environment or look into other configuration specifics that might be impacting xclip's ability to function correctly in your setup.

come back to 97

Could not make it work maybe it always expect a monitor ?

INSTALL AT START IS HERE

`rifaterdemsahin@oshost-vm:~$ cat /var/log/reboot.log
[2024-04-25 10:18:44] (root) Starting script execution...
[2024-04-25 10:18:44] (root) Adding xrdpsetup.sh to cron jobs at reboot...
[2024-04-25 10:18:44] (root) Current cron jobs:
@reboot /var/lib/waagent/custom-script/download/0/xrdpsetup.sh
[2024-04-25 10:18:44] (root) Running command: sudo apt-get update -y
Get:1 http://azure.archive.ubuntu.com/ubuntu noble InRelease [256 kB]
Get:2 http://azure.archive.ubuntu.com/ubuntu noble-updates InRelease [89.7 kB]
Get:3 http://azure.archive.ubuntu.com/ubuntu noble-backports InRelease [90.8 kB]
Hit:4 http://azure.archive.ubuntu.com/ubuntu noble-security InRelease
Get:5 http://azure.archive.ubuntu.com/ubuntu noble/main amd64 Packages [1401 kB]
Get:6 http://azure.archive.ubuntu.com/ubuntu noble/main Translation-en [513 kB]
Get:7 http://azure.archive.ubuntu.com/ubuntu noble/universe amd64 Packages [15.0 MB]
Get:8 http://azure.archive.ubuntu.com/ubuntu noble/universe Translation-en [5981 kB]
Get:9 http://azure.archive.ubuntu.com/ubuntu noble/universe amd64 Components [3871 kB]
Get:10 http://azure.archive.ubuntu.com/ubuntu noble/universe amd64 c-n-f Metadata [301 kB]
Get:11 http://azure.archive.ubuntu.com/ubuntu noble/restricted amd64 Packages [93.9 kB]
Get:12 http://azure.archive.ubuntu.com/ubuntu noble/restricted Translation-en [18.7 kB]
Get:13 http://azure.archive.ubuntu.com/ubuntu noble/multiverse amd64 Packages [269 kB]
Get:14 http://azure.archive.ubuntu.com/ubuntu noble/multiverse Translation-en [118 kB]
Get:15 http://azure.archive.ubuntu.com/ubuntu noble/multiverse amd64 Components [35.0 kB]
Get:16 http://azure.archive.ubuntu.com/ubuntu noble/multiverse amd64 c-n-f Metadata [8328 B]
Get:17 http://azure.archive.ubuntu.com/ubuntu noble-updates/universe amd64 c-n-f Metadata [112 B]
Get:18 http://azure.archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 c-n-f Metadata [116 B]
Get:19 http://azure.archive.ubuntu.com/ubuntu noble-backports/main amd64 c-n-f Metadata [112 B]
Get:20 http://azure.archive.ubuntu.com/ubuntu noble-backports/universe amd64 c-n-f Metadata [116 B]
Get:21 http://azure.archive.ubuntu.com/ubuntu noble-backports/restricted amd64 c-n-f Metadata [116 B]
Get:22 http://azure.archive.ubuntu.com/ubuntu noble-backports/multiverse amd64 c-n-f Metadata [116 B]
Get:23 http://azure.archive.ubuntu.com/ubuntu noble-security/universe amd64 c-n-f Metadata [112 B]
Get:24 http://azure.archive.ubuntu.com/ubuntu noble-security/multiverse amd64 c-n-f Metadata [116 B]
Fetched 28.1 MB in 5s (5327 kB/s)
Reading package lists...
[2024-04-25 10:18:59] (root) Running command: sudo apt install xclip -y

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
libice6 libsm6 libxmu6 libxt6t64 x11-common
The following NEW packages will be installed:
libice6 libsm6 libxmu6 libxt6t64 x11-common xclip
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 315 kB of archives.
After this operation, 1103 kB of additional disk space will be used.
Get:1 http://azure.archive.ubuntu.com/ubuntu noble/main amd64 x11-common all 1:7.7+23ubuntu3 [21.7 kB]
Get:2 http://azure.archive.ubuntu.com/ubuntu noble/main amd64 libice6 amd64 2:1.0.10-1build3 [41.4 kB]
Get:3 http://azure.archive.ubuntu.com/ubuntu noble/main amd64 libsm6 amd64 2:1.2.3-1build3 [15.7 kB]
Get:4 http://azure.archive.ubuntu.com/ubuntu noble/main amd64 libxt6t64 amd64 1:1.2.1-1.2build1 [171 kB]
Get:5 http://azure.archive.ubuntu.com/ubuntu noble/main amd64 libxmu6 amd64 2:1.1.3-3build2 [47.6 kB]
Get:6 http://azure.archive.ubuntu.com/ubuntu noble/universe amd64 xclip amd64 0.13-3 [17.6 kB]
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 315 kB in 0s (2872 kB/s)
Selecting previously unselected package x11-common.
(Reading database ... 68615 files and directories currently installed.)
Preparing to unpack .../0-x11-common_1%3a7.7+23ubuntu3_all.deb ...
Unpacking x11-common (1:7.7+23ubuntu3) ...
Selecting previously unselected package libice6:amd64.
Preparing to unpack .../1-libice6_2%3a1.0.10-1build3_amd64.deb ...
Unpacking libice6:amd64 (2:1.0.10-1build3) ...
Selecting previously unselected package libsm6:amd64.
Preparing to unpack .../2-libsm6_2%3a1.2.3-1build3_amd64.deb ...
Unpacking libsm6:amd64 (2:1.2.3-1build3) ...
Selecting previously unselected package libxt6t64:amd64.
Preparing to unpack .../3-libxt6t64_1%3a1.2.1-1.2build1_amd64.deb ...
Unpacking libxt6t64:amd64 (1:1.2.1-1.2build1) ...
Selecting previously unselected package libxmu6:amd64.
Preparing to unpack .../4-libxmu6_2%3a1.1.3-3build2_amd64.deb ...
Unpacking libxmu6:amd64 (2:1.1.3-3build2) ...
Selecting previously unselected package xclip.
Preparing to unpack .../5-xclip_0.13-3_amd64.deb ...
Unpacking xclip (0.13-3) ...
Setting up x11-common (1:7.7+23ubuntu3) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
Setting up libice6:amd64 (2:1.0.10-1build3) ...
Setting up libsm6:amd64 (2:1.2.3-1build3) ...
Setting up libxt6t64:amd64 (1:1.2.1-1.2build1) ...
Setting up libxmu6:amd64 (2:1.1.3-3build2) ...
Setting up xclip (0.13-3) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for libc-bin (2.39-0ubuntu8) ...

Running kernel seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
[2024-04-25 10:19:15] (root) Running command: sudo apt-get upgrade -y
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[2024-04-25 10:19:16] (root) Logging reboot action...
[2024-04-25 10:19:16] (root) - System is rebooting
[2024-04-25 10:19:16] (root) Rebooting the system...
[2024-04-25 10:19:16] (root) Reboot command issued.`

resources are working

come back to 98

favorite test both sides

come back to 99

come back to 100

come back to 101

if one does not work in one place try the other place before going back to part 2 ( distilled version ) https://wordpress.com/post/rifaterdemsahin.com/29268

htopp works different ui expertience

come back to 102

come back to 103

xclip works in the workstation where there is a monitor

come back to 104

move down with the part 2

come back to 105

Add new dashboard pin and go back to part 1 > https://wordpress.com/post/rifaterdemsahin.com/21783

come back to 106

Lets see if i can do the same with the images

come back to 107

This demo environment needed for the devops engineering show case the devaiops

come back to 108

Readh here to easy ingress point

come back to 109

I need to have these downloads

come back to 110

For downloading resources related to Red Hat OpenShift, including installers and images, you'll generally use the Red Hat Customer Portal or the OpenShift installation documentation. Here's a breakdown of what you might be looking for and how to find it:

  • OpenShift Installer: The OpenShift Installer is used to provision the infrastructure that OpenShift runs on. You can download the installer specifically configured for your environment (e.g., AWS, Azure, Google Cloud, VMware, bare metal) from the Red Hat Customer Portal.

  • Red Hat CoreOS (RHCOS): RHCOS is the container-optimized operating system built for running OpenShift. It integrates the container runtime and other components necessary for running OpenShift and is managed by the OpenShift cluster. Images for RHCOS can also be found on the Red Hat Customer Portal.

  • Secret Management: OpenShift uses secrets for managing sensitive information like passwords, OAuth tokens, and SSH keys. However, these are generally not downloadable; they are created and managed within the OpenShift cluster.

  • SCJOCOS Metal Image: It sounds like you might be referring to specialized images or configurations for running OpenShift on bare metal or similar environments. The usual term would be just "RHCOS images for metal installations". These can also be downloaded from the Red Hat Customer Portal.

To access these downloads:

  • You'll need to have a valid Red Hat subscription.

  • Visit the Red Hat Customer Portal.

  • Navigate to the Downloads section for OpenShift Container Platform.

  • Choose the version of OpenShift you are interested in.

  • From there, you can download the installer and RHCOS images for your specific deployment type (cloud, virtualized environments, or bare metal).

If you have any more specific questions or need detailed guidance on the installation process, I can help with that too!

Get the one for the Azure

come back to 111

I have the 22 he has the 20 >>> he olso uses the iso !

come back to 112

networking

he also mixes up with the vmware workstation

come back to 113

Network as the base

come back to 114

he adds his keys for practical access

come back to 115

Creates 6 vms in the back

come back to 116

get to this stage to be able to see your box is online

come back to 117

not only one

come back to 118

now the dns makes more and more sense

come back to 119

boxes to talk to each other

come back to 120

Pull secret link

come back to 121

come back to 122

https://access.redhat.com/solutions/4844461

come back to 123

come back to 124

https://console.redhat.com/openshift/create

come back to 125

come back to 126

come back to 127

come back to 128

Save to last pass

https://console.redhat.com/openshift/install/azure/user-provisioned

Different ways to install the credentials

come back to 129

Secret gets passed over to text file

come back to 130

Openshift initial files with the ssh keys

come back to 131

haproxy.cfg

come back to 132

Worker install looks straight forward

come back to 133

moving the code with the scripts >>> makes sense the hands on

come back to 134

come back to 135

your own registry comes on line >>> logic apps create > release > destroy part trick >>> to get the project!

come back to 136

First principles fixes

come back to 137

these are running on the host so have your host enviroment in the local

and have a file to run them as well

come back to 138

Host setup is also taking the time

come back to 139

Turning the host to the action

come back to 140

added a file called host setup

come back to 141

7m > watched nana and most 0.01 got placed!

main yaml part is in

come back to 142

apache server in your network and have your own truth

come back to 143

Metal image

come back to 144

runs manually without a workflow by hand

come back to 145

get hsproxy the host and the apache is the main goal

come back to 146

on host setup

come back to 147

Than run the bootstrap which he moved on to the workstation

come back to 148

bootstrapper gets deleted

come back to 149

focus on basics ( part 3 ) >>> does not make sense to take all in ! >>> push it to the bottom

Registry Install

come back to 150

Apache Install

come back to 151

It seems you've uploaded an image of a script intended to create a cluster for OpenShift Sandbox with a DNS primary zone. I can help you understand the script by explaining the steps. Here is a breakdown of the script commands:

  • The script defines variables for the domain and cluster name to be used throughout the setup process.

  • It appears to have a command that adds a DNS domain to the DNS server. This is typically done to resolve the cluster's domain name to the correct IP addresses.

  • There is also a mention of adding the domain to the DNS server's primary zone file, which means that it would become the authoritative source for information about this domain.

  • Additionally, the script references setting up an external DNS. This implies that the script is making sure that the DNS settings are also updated in a location that is publicly accessible, not just within a private network.

  • There are some commented lines and notes in the script which seem to be instructions or explanations for the user.

  • The PowerShell commands at the bottom indicate that the user is starting some process related to the OpenShift developer sandbox from the PowerShell console. This might be related to configuring the OpenShift environment.

The specific details and how to execute them depend on your DNS server setup, the OpenShift configuration, and your environment. If you want a detailed explanation of each command and how to adapt it for your needs, you could share the text from the script, and I could provide more detailed guidance.

Now getting it live server has all the next next part in it

come back to 152

Script > should be able to get the all the ipp adresses created and set the dns records

if i can do it with logic apps that is great!

come back to 153

mimic this

come back to 154

To create a PowerShell script that sets up an OpenShift Sandbox with a primary DNS zone, you would need to write a script that:

  • Defines the domain and cluster name.

  • Adds the domain to your DNS server with a primary zone.

  • Starts the OpenShift installation process with the specified settings.

Below is a template for a PowerShell script that you might use as a starting point. Please note that this is a hypothetical example and would need to be adapted to your specific environment and DNS server configuration. You should replace the placeholders with the actual values specific to your setup.

Define domain and cluster name

$DomainName = "example.com"
$ClusterName = "openshift"

Base domain for DNS

$BaseDomain = "sandbox.$DomainName"
$ClusterHostname = "api.$ClusterName.$BaseDomain"

IP Address for the OpenShift API - Replace with the actual IP address

$ApiIpAddress = "192.0.2.1"

Adding a primary zone to DNS - This assumes you are using Windows DNS. Adjust if using another DNS service

Add-DnsServerPrimaryZone -Name $BaseDomain -ZoneFile "$BaseDomain.dns"

Adding a DNS A Record for the OpenShift API

Add-DnsServerResourceRecordA -Name "api" -ZoneName $BaseDomain -IPv4Address $ApiIpAddress

Starts the OpenShift installation process

You need to replace with the actual command to start the OpenShift installation

This usually involves running an installer script or command with a configuration file

For example:

Start-Process -FilePath "openshift-install" -ArgumentList "create cluster --dir=./$ClusterName --log-level=info"

Please note: You must have the OpenShift CLI installed and properly configured on your machine.

Consult the OpenShift documentation for the exact installation procedure as it varies by version and environment.

Remember that to run this script, you'll need to have appropriate permissions on the DNS server and the machine where the script is executed. Also, the commands may vary if you're not using Windows DNS Server or if your OpenShift setup has specific requirements.

Make sure to consult your DNS provider's documentation for the exact commands to use and the OpenShift installation guide for detailed instructions on deploying a cluster.

come back to 155

forcing myhand with the logic apps

come back to 156

This part comes in with the gpt

your goal read understand and iterate

Certainly! In PowerShell, you can create a function called AddOcpDns that encapsulates the functionality for adding the necessary DNS records for an OpenShift cluster. Below is an example function that you might include in your PowerShell script. Please note that this example assumes you are using Windows DNS Server and have the required DNS PowerShell module available.

function AddOcpDns {
param (
[string]$BaseDomain,
[string]$ClusterName,
[string]$ApiIpAddress,
[string]$AppsWildcardIpAddress
)

# Define the API and apps DNS names
                $ApiDnsName = "api.$ClusterName.$BaseDomain"
                $AppsDnsName = "*.apps.$ClusterName.$BaseDomain"
                
                # Adding a primary zone to DNS
                Add-DnsServerPrimaryZone -Name $BaseDomain -ZoneFile "$BaseDomain.dns"
                
                # Adding a DNS A Record for the OpenShift API
                Add-DnsServerResourceRecordA -Name "api" -ZoneName $BaseDomain -IPv4Address $ApiIpAddress -CreatePtr
                
                # Adding a DNS A Record for the apps wildcard
                Add-DnsServerResourceRecordA -Name "*" -HostNameAlias $AppsDnsName -ZoneName $BaseDomain -IPv4Address $AppsWildcardIpAddress -CreatePtr
                
                Write-Host "DNS records for OpenShift have been added:"
                Write-Host "API URL: $ApiDnsName"
                Write-Host "Apps wildcard URL: $AppsDnsName"
                

}

Usage example:

Replace these values with your actual domain name, cluster name, API IP, and apps wildcard IP.

$yourBaseDomain = "example.com"
$yourClusterName = "openshift"
$yourApiIpAddress = "192.168.1.10" # The IP address of the OpenShift API endpoint
$yourAppsWildcardIpAddress = "192.168.1.11" # The IP address for the apps wildcard DNS record

Call the function with the parameters

AddOcpDns -BaseDomain $yourBaseDomain -ClusterName $yourClusterName -ApiIpAddress $yourApiIpAddress -AppsWildcardIpAddress $yourAppsWildcardIpAddress

This script defines the AddOcpDns function, which takes four parameters: BaseDomain, ClusterName, ApiIpAddress, and AppsWildcardIpAddress. Inside the function, it sets up a DNS primary zone for the base domain, adds an A record for the OpenShift API endpoint, and adds an A record for the wildcard domain used by OpenShift apps.

When using this function, replace the ApiIpAddress and AppsWildcardIpAddress with the actual IP addresses for your OpenShift API and the wildcard domain for apps, respectively.

Remember to run this script with administrative privileges since it makes changes to the DNS server configuration. Before running the script, ensure that your DNS server and environment are properly backed up and that you have tested these commands in a non-production environment.

A;ll in the name for the enterprise IT to run a high avaible cluster!

Easier and visual route for me to iterate for the machines there

come back to 157

also add what you learned

come back to 158

SRV (Service) records are a type of DNS (Domain Name System) record that is used to identify servers that host specific services. They are used to locate services such as Voice over IP (VoIP), messaging, and other services within a domain. Here are some reasons why SRV records are used:

  • Service Discovery: SRV records enable service discovery. They provide a way for clients to query a DNS server to find out the hostname and port number of servers providing specific services.

  • Load Distribution and Fault Tolerance: SRV records can specify multiple servers for a service, each with a priority and weight. This allows clients to choose the best server based on the priority and to distribute the load among servers with the same priority using the weight parameter.

  • Flexible Service Hosting: Services can be moved to different servers without changing the client configuration. For example, if you move a service to a new IP address, you only need to update the SRV record instead of updating the configuration on each client.

  • Protocol Specification: SRV records contain the protocol used by the service, which allows the same service to be offered over different protocols.

  • Port Specification: Since SRV records include the port number, services can run on non-standard ports, and clients can still discover and connect to them without knowing the port in advance.

  • Use with TLS and SSL: SRV records can be used to direct traffic to secure ports and facilitate the use of SSL/TLS for the service in question.

  • Integration with Active Directory: In Microsoft's Active Directory, SRV records are used extensively to locate domain controllers and other critical AD services.

Here's an example of what an SRV record might look like:

_service._proto.name. TTL class SRV priority weight port target.

For example, for a SIP service, it might be:

_sip._tcp.example.com. 3600 IN SRV 10 50 5060 sipserver.example.com.

In the context of OpenShift or any Kubernetes-based system, SRV records can be useful for helping services locate and communicate with each other within the cluster or from outside the cluster. OpenShift uses DNS for service discovery within the cluster, and SRV records can be a part of this process if services need to be exposed or located in a more complex networking environment.

There is a reader there I am less lonely ?

come back to 159

everything came up

come back to 160

Asisted installer steps

come back to 161

Service principal management

come back to 162

ARO > Secret looks like it is loaded that way complex market place practice

come back to 163

come back to 164

come back to 165

come back to 166

ARO stands for Azure Red Hat OpenShift, which is a joint collaboration between Microsoft Azure and Red Hat to provide a managed OpenShift service hosted on the Azure cloud platform. ARO simplifies the deployment, management, and operations of OpenShift, which is an enterprise Kubernetes platform, allowing users to run containerized applications at scale and with greater security.

Here's why ARO is significant:

  • Simplified Operations: ARO manages the OpenShift cluster's infrastructure, reducing the operational overhead for users. Microsoft and Red Hat handle maintenance, updates, and patching, leaving users free to focus on their applications.

  • Integrated Support: Users get integrated support from both Microsoft and Red Hat, streamlining the process of getting help when needed.

  • Security and Compliance: ARO is built with security in mind, featuring integrated compliance and regulatory features that follow Microsoft's and Red Hat's security best practices.

  • Scalability: Users can scale their applications more easily due to Azure's cloud infrastructure.

  • Hybrid Cloud: ARO fits well into a hybrid cloud strategy, offering consistent services and tooling between on-premises environments and the Azure cloud.

Regarding secrets in the context of ARO, or OpenShift in general, a secret is a resource used in Kubernetes and OpenShift to hold sensitive information, such as passwords, OAuth tokens, ssh keys, etc. Secrets are used for several reasons:

  • Security: Secrets are intended to hold sensitive data, which should be protected from unauthorized access and should not be stored in plain text, especially within the application code.

  • Confidentiality: By using secrets, sensitive data is segregated from the application code and can be managed independently. Only the necessary workloads and roles have access to them.

  • Management: Secrets provide a central mechanism to manage sensitive data and can be rotated, updated, and revoked without modifying the application code.

  • Flexibility: Secrets can be mounted as data volumes or exposed as environment variables to be used by applications running in a container.

When an OpenShift cluster is created within Azure (ARO), various secrets are required for configuration, including those that allow the cluster to authenticate with Azure services and those that secure the communication between cluster components. Proper handling of secrets is a cornerstone of maintaining a secure and well-functioning OpenShift environment.

as at the core helps the process

come back to 167

setting up ingress

come back to 168


Oc Commands

come back to 169

Api and Grafana Relationshio

come back to 170

Kubeconfig

come back to 171

Different views

come back to 172

Visual pod creation

come back to 173

Helm

come back to 174

Helms wordpress

come back to 175

Storage

come back to 176

MASTER TODOS

  • network ( FOCUS )

Script to create in Azure

domain

  • subnets

  • aro

  • A logic app to create the remaining cluster

3 worker nodes

  • 3 Master nodes

  • Set dns names to all machines

start with one addocpdns

  • set a records for OCP

  • and srv records systems to talkt o each other over ports

  • apache

Script to create in linux

sudo apt update

  • sudo apt install apache2 -y

  • Add this to bootstrap code in storage

  • Use scp to access the machine

SIDE TASKS

  • Bootstrapping

Trigger

  • Monitor

  • set servcice principals

  • Install workers with script

move install code with scp

  • fix line ending with dos2unix

  • create manigest and schedule workloads

  • Controllers

use ioc commands

  • join worker nodes

  • kubeconfig

  • Automate cluster

turn off machines

  • static mapping for api and *.apps

  • Yaml repository

os-install/manifests

  • registry install

  • ingress setup

  • licence install

see expriy

  • see cluster in redhat.com type ocp ( openshift container platform )

  • ha proxy

Create a config file

  • To see on one machine

Start with local workstation

  • see control plane master and worker

  • Storage

deploy apps

  • seperate their storage

  • dashboard

see all cluster in the dashboard in azure

  • use different views in OS

  • visual pod creation

  • OC commands

oc new-project

  • microservice deploy

  • add it to devops.engineering

  • the enginer is the kubernetes in the train

  • Helm

bring complex elk like monitorung tools

  • wordpress

Imported from rifaterdemsahin.com · 2024