Hey, apologies for the issue but I found your repo from this article you wrote: https://dustymabe.com/2020/08/13/openshift-okd-on-fedora-coreos-on-digitalocean-part-1-deployment

This article/repo are very biased to users that have previous knowledge and experience of Digital Ocean, and as such it's not easy to get an instance stood up. So far my current problems have been:

You need to have at least one droplet stood up, tagged with the same cluster name you want to use in your OKD4 cluster otherwise you cannot use the firewall.

I'm having issues getting a cluster running. After looking into it, it seems like a strange networking/ipv6 issue after the pivot.

On first boot, before the droplet automatically restarts, networking works fine and I can ping google:
rpm-ostree status

State: idle
Deployments:
● ostree://fedora:fedora/x86_64/coreos/stable
                   Version: 33.20201214.3.1 (2021-01-05T00:05:03Z)
                    Commit: a64854cbcec13e1c3b3ccbfd3802e377e23c0c136d384c32736addf77e0e2a03
              GPGSignature: Valid signature by 963A2BEB02009608FE67EA4249FD77499570FF31

After the droplet restarts:
journalctl -b -f -u release-image.service -u bootkube.service

Jan 06 06:39:22 bootstrap release-image-download.sh[95700]: Error: Error initializing source docker://quay.io/openshift/okd@sha256:01948f4c6bdd85cdd212eb40d96527a53d6382c4489d7da57522864178620a2c: error pinging docker registry quay.io: Get "https://quay.io/v2/": dial tcp: lookup quay.io on [::1]:53: read udp [::1]:48271->[::1]:53: read: connection refused

rpm-ostree status

State: idle
Deployments:
● pivot://quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829
              CustomOrigin: Managed by machine-config-operator
                 Timestamp: 2020-12-12T05:05:37Z

  ostree://fedora:fedora/x86_64/coreos/stable
                   Version: 33.20201214.3.1 (2021-01-05T00:05:03Z)
                    Commit: a64854cbcec13e1c3b3ccbfd3802e377e23c0c136d384c32736addf77e0e2a03
              GPGSignature: Valid signature by 963A2BEB02009608FE67EA4249FD77499570FF31

When i run the script to deploy okd the following error happens:

make_bucket failed: s3://mycluster.mydomain An error occurred (XAmzContentSHA256Mismatch) when calling the CreateBucket operation: Unknown

If i create the bucket in the DO GUI to pass this error the script return just Bucket already exists... then the script is terminating..

make_bucket failed: s3://mycluster.mydomain An error occurred (BucketAlreadyExists) when calling the CreateBucket operation: Bucket already exists

I couldnt see an error handling in your code for this case. I also checked it out when i try to create the spaces with aws CLI. So the error comes from AWS CLI.

aws --endpoint-url $SPACES_ENDPOINT s3 mb $SPACES_BUCKET
make_bucket failed: s3:// Parameter validation failed:
Invalid bucket name "": Bucket name must match the regex "^[a-zA-Z0-9.-_]{1,255}$" or be an ARN matching the regex "^arn:(aws).:(s3|s3-object-lambda):[a-z-0-9]+:[0-9]{12}:accesspoint[/:][a-zA-Z0-9-]{1,63}$|^arn:(aws).:s3-outposts:[a-z-0-9]+:[0-9]{12}:outpost[/:][a-zA-Z0-9-]{1,63}[/:]accesspoint[/:][a-zA-Z0-9-]{1,63}$"

A Fix for this issues would be nice.

#54~20.04.1-Ubuntu with:
AWS
DOCTL
OC
OPENSHIFT-INSTALL

Trying to install okd 4.7 using this process on Digital Ocean. Had previously got it working with 4.4 but having loads of problems with 4.7 :(

It looks to me like the DNS setup is now different as the etcd specific records are not required and the installer relies on PTR records to configure etcd now. I seem to be having major conflicts between some etcd components using the control droplets' private ip and some using the public ip for the etcd configuration

Has anyone using this got it working on DO with okd 4.7 ?

I noticed in line 289 & 304 in digitalocean-okd-install the public ip is used for creating the dns records.
Is there a reason for using the public ip instead of the private ip of the droplet? Is this due to some limitation with digitialocean?

Hi, im trying to follow the guide but the script returns the following error:
make_bucket failed: s3://okd.latapps.com.ar An error occurred (XAmzContentSHA256Mismatch) when calling the CreateBucket operation: Unknown

Hi, im trying to follow your guide, i've install everything (doctl, aws) and everything runs ok on console, but when I try to start the ./digitalocean-okd-install I got a message saying: No aws. Can't continue, even thou it's installed a runing fine.

You mention in your youtube video as well as this commit cdeb929 that you hacked it to only one use load balancer. Thoughts on implementing the "best practice" way?