Demo: How to try out single-node OpenShift from Red Hat

Поділитися
Вставка
  • Опубліковано 13 вер 2024
  • Learn how you can install a single node OpenShift using the assisted-installer portal - a console.redhat.com hosted service that simplifies and streamlines the deployment experience of Red Hat OpenShift.
    Try it at console.redhat.com

КОМЕНТАРІ • 18

  • @FlexibleToast
    @FlexibleToast 3 роки тому +4

    Is this available for OKD yet? That would be awesome for homelabbers that are likely to use a system longer than 60 days.

  • @benoukhanov6320
    @benoukhanov6320 3 роки тому +1

    Very cool demo, thank you!

  • @saygin123
    @saygin123 3 роки тому +1

    Good job ! Is there any predicted date for the Assisted Installer that it becomes fully supported.

  • @JohnMatthew1
    @JohnMatthew1 3 роки тому

    Nice job, and thank you for posting this!

  • @dometdemont
    @dometdemont 3 роки тому

    Outstanding feature, thanks much. Successfully tested on HPE ProLiant DL110 Gen10 Plus. Any chance to get an
    OpenShift Container Storage operator deployable on one single baremetal node instead of 3?

  • @paulohenriqueluizetto9946
    @paulohenriqueluizetto9946 3 роки тому

    Nice! Thank you.

  • @cryptout
    @cryptout 2 роки тому

    Did anyone succeed installing this on VirtualBox?

  • @uliwallscheid6399
    @uliwallscheid6399 2 роки тому

    Hi, i cannot get past 80% installation and i have tried multiple approaches/times. I'm trying to deploy on a VM. It always fails deploying OPenShift operators in the end.

    • @uliwallscheid6399
      @uliwallscheid6399 2 роки тому

      Error message: Operator cvo status: progressing message: Unable to apply 4.10.11: some cluster operators have not yet rolled out.
      Tried a physical server now (HPE ProLiant DL380G9).

    • @uliwallscheid6399
      @uliwallscheid6399 2 роки тому

      Where's the problem? Happen's on other releases as well: Operator cvo status: progressing message: Unable to apply 4.8.29: some cluster operators have not yet rolled out

    • @janjurak5905
      @janjurak5905 Рік тому

      i have exactly the same experiance. And i tried many times, because there was oportinutity job. Clusters are very complex stuff and doing for them releasing so bad quality is very painful especially for new ppl my type. But OK, it's complex, but when failed for me simple iso created for single node cluster (i just picked the most trivial option after series of failures) and anstaller failed during making DNS queries and by mistake took domain of 3 levels as 2 levels - i only feel disrespect. it's not only about have there all new features first, it's also about quality of release you submit your users. I liked multiple ideas, but it is too much for me. take care, no hard feelings

  • @vvsha1980
    @vvsha1980 3 роки тому

    How do I give static IP and hostname to SNO baremetal node if I don’t have DHCP and DNS

    • @bobby07241
      @bobby07241 3 роки тому

      you need dhcp for the initial setup is mandatory

    • @johncall7703
      @johncall7703 3 роки тому +3

      I was able to use the Assisted Installer method in an environment without DHCP. This likely isn't supported, but it works for me. When the Discovery Image ISO is booted you need to interrupt the GRUB boot loader (see timestamp 6:01 of this video) and use kernel command-line arguments to setup networking. You may have to do this one last time when the system reboots. Here is an example of the kernel command-line arguments I used, if you need more info please refer to the man page for dracut.cmdline (e.g. "man dracut.cmdline")
      ip=172.31.255.101::172.31.255.1:255.255.255.0:ocp.home.lab:enp1s0:none nameserver=172.31.255.10
      ip=:[]:::::{none|off|dhcp|on|any|dhcp6|auto6|ibft}[:[][:]]

    • @tynguyen1236
      @tynguyen1236 3 роки тому

      @@johncall7703 Hi John,
      As i don't have DHCP so i need to setup static IP as per your advice, so please could you provide the sequence to interrupt the GRUB boot loader and the dracut.cmdline access to the menu if needed for adding the ip as indicated.
      Many thanks

    • @JohnCall-LovesLinux
      @JohnCall-LovesLinux 3 роки тому

      @@tynguyen1236 I believe all of those details about how to interrupt grub and what to add to the kernel command line was provided in my initial comment. Did you watch the video at the 6:01 time? Did you read the bottom of my comment with the `ip=... ` example?

    • @invokerfury1811
      @invokerfury1811 2 роки тому

      @@johncall7703 if machine restart itself cause power fault.. i need to do this again?