docs: update README.md

Signed-off-by: Shantanoo 'Shan' Desai <[email protected]>

Author: shantanoo-desai

README.md

@@ -6,7 +6,8 @@ Currently Supported Images:
 | Name                | Version       |
 |:--------------------|:-------------:|
 | __Focal Fossa__     |     `20.04.6` |
-| __Jammy Jellyfish__ |     `22.04.2` |
+| __Jammy Jellyfish__ |     `22.04.4` |
+| __Noble Numbat__    |     `24.04`   |
 
 An accompanying blogpost is available [here][1]
 
@@ -22,13 +23,19 @@ To validate `cloud-init` and `ubuntu.pkr.hcl` template perform
 make validate
 ```
 
-To simply validate `cloud-init`
+To simply validate `cloud-init` against all distros
 
 ```bash
 make validate-cloudinit
 ```
 
-To simply validate `ubuntu.pkr.hcl` template (against both `focal` and `jammy`)
+To validate `cloud-init` configuration of a specific distro (`focal`, `jammy`, `noble`)
+
+```bash
+make validate-cloudinit-<distroname> # <distroname> here is either focal, jammy or noble
+```
+
+To simply validate `ubuntu.pkr.hcl` template against all distros
 
 ```bash
 make validate-packer
@@ -48,9 +55,19 @@ to build Ubuntu 22.04 (Jammy) image
 make build-jammy
 ```
 
+to build Ubuntu 24.04 (Noble) image
+
+```bash
+make build-noble
+```
+
 ## UEFI BootLoader Sequence Determination
 
 see the `late-commands` in the `user-data` file. This is determined by installing `efibootmgr` on the live
 image and performing `sudo efibootmgr`. This lists what are the sequences and when should the image be booted.
 
+> NOTE: there seems to be compatibility issue between Ubuntu 24.04 and older Ubuntu LTS version in terms of
+> output from the `efibootmgr`, namely, Capitalization. Hence each Cloud-Init `user-data` now is in a 
+> separate directory under the `http` directory in the repo.
+
 [1]: https://shantanoo-desai.github.io/posts/technology/packer-ubuntu-qemu/