Hi,
As far as I remember, ETCD records (A + SRVs) are not needed anymore and
can safely be removed.
And I'm not sure why ocp.stg & apps.ocp.stg are needed ? *.apps.ocp.stg
should be enough, I think, but I may miss something here.
On 2021-07-12 19:35, David Kirwan wrote:
Hi folks,
We're hopi
On 2021-07-13 02:33, Kevin Fenzi wrote:
ocp -> console "app"
.apps.ocp -> each application...
So, I think both are needed.
Oh ok, that make senses.
On OCP4, by default, console is also behind apps (something like
console-openshift-console.apps) but I get why you would want to change
that :)
Hi,
I think the A record for worker01.ocp.stg.iad2.fedoraproject.org is
missing.
On 2021-07-21 12:00, David Kirwan wrote:
https://gist.github.com/davidkirwan/ae4038fa101dea3e8e1318ce3330970b
Hi infra, can I please get a review on the patch above, we are
configuring the ocpstaging worker mach
On 2021-09-23 07:44, Fabian Arrotin wrote:
On 23/09/2021 02:55, Neal Gompa wrote:
On Wed, Sep 22, 2021 at 7:12 PM Kevin Fenzi wrote:
* Should we now delete the kubeadmin user? In 3.x I know they advise
to
do that after auth is setup.
I'm not sure that's a good idea. I'm not even certain
Hi everyone,
I have a PR https://pagure.io/fedora-infra/ansible/pull-request/823 to
fix translated versions of getfedora.org that doesn't work properly
anymore (see https://pagure.io/fedora-web/websites/issue/202)
That would be nice if I could get +1 to get this merged before the
release.
_
On 2021-10-20 21:05, Kevin Fenzi wrote:
Greetings everyone.
So, we now have openshift 4 clusters for both prod and stg and I think
(although correct me if I am wrong) they are all checked out and ready
to handle apps. :)
That's good news :)
To move an app over:
* stop all the apps pods in
On 2021-10-23 22:36, Kevin Fenzi wrote:
I'm not sure what antora version. I think it's whatever is in f34, but
perhaps someone else can chime in with the exact version and how to
find
it.
It's using the latest stable version of antora 2.3:
https://pagure.io/fedora-docs/docs-fp-o/blob/prod/f
ll run the openvpn process and since the openshift router
listen on all interfaces by default, it should be available through the
vpn automagically.
darknao
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send a
On 2022-06-07 21:24, Kevin Fenzi wrote:
Hum... that sounds reasonable, but I am not sure what the details would
look like. ;( Would that be in openshift-ingress?
Not necessary. Ideally it would be in its own namespace.
I've took a closer look and I think you will need the following:
- pod runni
On 2022-06-09 00:58, Kevin Fenzi wrote:
Another issue I thought of: with openvpn each client has its own set of
certs. so, each pod needs just the ones for that node...
I thought of that too. You can either use one
deployment+configmap+secret combo
for each node or, my favorite, use a single
On 2022-06-17 22:56, Kevin Fenzi wrote:
We have a few apps that rebuild/deploy on git changes, which is fine,
but doesn't do anything to keep their container env up to date/secure.
We have a number of apps that tigger on imagestream changes, but as far
as I can tell thats only changes in their
].
Any +1s?
[1]: https://fedoraproject.org/wiki/Changes/RestoreCloudEdition
[2]: https://pagure.io/fedora-infra/ansible/pull-request/1240
Thanks,
-darknao
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an
Hey!
I'm not sure it's worth doing. While I don't think this is a bad idea, I
can't find any real gains to a shared instance in an Openshift world.
I do see a few downsides though:
- You'll need to share the same redis password across several projects.
I see that as a potential security issue.
On 2022-11-24 18:58, Jan K wrote:
What is likelyhood of Openshift going down? A would be best
solution if stable enough.
copperi
Openshift is quite stable. But everything around it may not. Having a
network outage, internal VPN issue, datacenter incident, or just an
openshift migration
direct access to our
proxies.
I feel like I've somewhat answered my own question, but I would love
your opinion on this :)
-darknao
On 2022-11-24 18:59, Ahmed Almeleh wrote:
My vote is for C. If we can reduce the amount of steps required to
implement service redundancy. Deployment to S
cess to openshift
could
fix.
That's a valid point.
I think I'll go with B as a starting point. We could always build from
there at a later time, as we see fit.
-darknao
___
infrastructure mailing list -- infrastructure@lists.fedoraproj
If you need max perf and single access (like a PSQL
database), use RBD. If you want your data accessible from outside
Openshift (i.e: on another VM), use NFS.
With the exception of S3, all other storage types are used the same way.
Only the PVC definition is differ
]: https://fedoraproject.org/
Thanks!
-darknao
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US
Thanks, everyone!
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
Congrats Adam!
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
Li
On Tuesday, September 5th, 2023 at 21:53, Kevin Fenzi wrote:
> I already have the cert ready to push into ansible-private, just need
> +1's to run the proxies playbook and update the cert there.
>
+1
___
infrastructure mailing list -- infrastructure@l
Hi,
There was an issue with our OpenID service that is now fixed.
If you still have issues logging in, please open a ticket at
https://pagure.io/fedora-infrastructure/issues
On Saturday, 27 January 2024 at 10:03, Yanko Kaneti wrote:
>
>
> Hello,
>
> Trying to login to Pagure.io at
> https:
+1 from me.
-darknao
--
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of
On Wednesday, 6 March 2024 at 18:36, Kevin Fenzi wrote:
> So, I'd like to build this for f39 (which our compose hosts are) and
> update them.
>
> If something goes very wrong we should be able to just downgrade back to
> the previous version.
>
> +1s?
+1
--
___
On Wednesday, 20 March 2024 at 21:16, Kevin Fenzi wrote:
>
> So, can I get +1s to:
>
> apply this to koji builders
> restart kojid on them
>
+1
--
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an emai
On Wednesday, 20 March 2024 at 03:41, Ryan Lerch wrote:
> Working on switching kerneltest over to openshift, and the final step
> is to update the proxies:
>
> https://pagure.io/fedora-infra/ansible/pull-request/1872
>
> and then also run the iplison playbook so the oidc config gets copied
> ov
On Friday, 29 March 2024 at 10:48, Aurélien Bompard
wrote:
>
> Hey folks!
>
> Yesterday the os-control01.stg machine was reinstalled as RHEL9.
> Unfortunately there was a script on there that I forgot to backup. I
> would like, if possible, to retreive it.
> The old VM disk is still on the VM
I've extracted the file for you on vmhost-x86-11 in /tmp
-rw-r--r--. 1 root root 4499 Mar 29 10:33 /tmp/jobs-summary
--
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.f
On Monday, 8 April 2024 at 18:25, Kevin Fenzi wrote:
> So, I'd like to update all the builders to the latest f39-infra koji
> package with these patches and restart kojid on them.
>
> +1s?
>
+1
--
___
infrastructure mailing list -- infrastructure@lis
edora-infra/ansible/pull-request/1968
Any +1s?
-darknao
--
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On Thursday, 18 April 2024 at 23:14, Kevin Fenzi wrote:
> Is that the last of the 'old' sites now?
alt.fedoraproject.org is the last, and next one on my list.
--
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe s
On Monday, 22 April 2024 at 12:45, Aurélien Bompard
wrote:
>
>
> Hey folks,
>
> With Ryan we have deployed the refreshed badges stack in prod openshift,
> as the badges components are not frozen. However, the proxies are, and
> we need to update them to point at openshift instead of VMs.
> I'
On Tuesday, 23 April 2024 at 12:49, David Kirwan wrote:
> I want to add the Zabbix agent to the systems in the ansible group: `logger`.
> Requesting a freeze break, to make this change and then run the playbook:
> `groups/logserver.yml`
>
+1 from me
--
+1
On Friday, 30 August 2024 at 18:01, Kevin Fenzi wrote:
>
>
> Greetings
>
> I'd like to update pungi on compose-branched01 from pungi-4.7.0-1.fc40
> to pungi-4.7.0-3.fc40.
>
> The changelog is:
>
> * Thu Aug 29 2024 Lubomír Sedlář lsed...@redhat.com - 4.7.0-3
>
> - Backport patch for
34 matches
Mail list logo
