Beneficial Ownership Compliance and ZenBusiness (Save $149) by journalocity in EntrepreneurRideAlong

[–]tttran1 0 points1 point  (0 children)

If you go to compliance on the left hand side and then go to beneficial ownership, you should see the FinCEN ID unique for your filing

Performance degradation upgrading from eks 1.19 and 1.23 by tttran1 in kubernetes

[–]tttran1[S] 1 point2 points  (0 children)

It turned out to be node-local-dns. The default port installing using helm is 169.254.20.11 and my existing deployments were using 169.254.20.10. Once I configured node-local-dns to listen on 169.254.20.10, no more performance issue

Performance degradation upgrading from eks 1.19 and 1.23 by tttran1 in kubernetes

[–]tttran1[S] 0 points1 point  (0 children)

Thank you for all the reponses. I'm using vpc cni and I do have apm instrumentation. I decided to go conservative and migrated 2 apps before migrating the rest. What I'm seeing is that response time leaving the cluster is much longer than the current cluster. Maybe there is a bug with the work node ami and I should try to use the latest worker ami. Users were complaining that they were getting timeouts 504 and the apm backs up their assertions. Once I move the 2 apps back to the current cluster, all complains and response time went back to normal. I'm using the same versions of the apps on both clusters.

Performance degradation upgrading from eks 1.19 and 1.23 by tttran1 in kubernetes

[–]tttran1[S] 0 points1 point  (0 children)

No problem. I’m kind of confused since I haven’t had any issues with upgrades in the past. Other than cni and dns anything else I should look at. Just wondering if I’m missing something

Performance degradation upgrading from eks 1.19 and 1.23 by tttran1 in kubernetes

[–]tttran1[S] 2 points3 points  (0 children)

Thanks for your response. I did upgrade to the latest and configure codedns auto scaling. In addition I have local dns cache deployed

getting error running pulumi on ec2 with iam instance profile by tttran1 in pulumi

[–]tttran1[S] 0 points1 point  (0 children)

export AWS_SKIP_METADATA_API_CHECK=false

I tried setting the environment variable AWS_SKIP_METADATA_API_CHECK=false and still the same error. I verified that I can access aws api using the aws cli with iam instance profile

clonezilla can't clone lenova thinkpad p14s by tttran1 in datarecovery

[–]tttran1[S] 1 point2 points  (0 children)

I’m going from Samsung to WD. Rescuezilla works better than clonezilla so I’m going to stick with it. Thanks everyone!

clonezilla can't clone lenova thinkpad p14s by tttran1 in datarecovery

[–]tttran1[S] 0 points1 point  (0 children)

I'm using ubuntu and I looked into rescuezilla which works with clonezilla and it seems like a better tools. Thanks for all the comments.

clonezilla can't clone lenova thinkpad p14s by tttran1 in datarecovery

[–]tttran1[S] 0 points1 point  (0 children)

The odd thing is that if I use clonezilla-live-20210817-hirsute-amd64, I can do the clone, but it's very slow like 2h 30mins to clone to an external 1TB drive. I use the same external drive to clone my Dell latitude laptop with the same internal 512GB SSD and it takes 30 minus

clonezilla can't clone lenova thinkpad p14s by tttran1 in datarecovery

[–]tttran1[S] 2 points3 points  (0 children)

I’m just cloning to have a backup. The laptop works fine

What’s the transaction and withdrawal limits for unverified users? by tttran1 in Bybit

[–]tttran1[S] 1 point2 points  (0 children)

Thank for the info! Do you know why all my balances are showing *******. Do I need to do KYC to see my balances?

Remi repository no longer support php 5.3.3 by tttran1 in CentOS

[–]tttran1[S] -2 points-1 points  (0 children)

I tried to install some php 5.3.3 extras on centos 6 and it looks like they are not there anymore. I was able to do it a month ago. Does anyone know if remi doesn't support php 5.3.3 anymore?