Add Kustomize artifacts for deploying rsyslog

[accorvin]

No description provided.

[todo]

move PID to top level

internal-data-hub/rsyslog/bases/rsyslog/rsyslog-conf/25-viaq-common.conf

Lines 52 to 57 in efb42d0

	# The imjournal normalized _PID to pid in its message properties. TODO: move PID to top level
	set $.fwdpid = $!pid;
	} else {
	if strlen($!_PID) > 0 then {
	set $.fwdpid = $!_PID;
	}

---

This comment was generated by todo based on a TODO comment in efb42d0 in #1. cc @accorvin.

[HumairAK]

one minor comment above, but other than that lgtm!

[anishasthana]

Can we bring the contents of this repository out as well? Or should it stay internal for now?

[accorvin]

@anishasthana I've been trying to think of a good solution for that. If I can get a repo set up in a good spot in Quay, what do you think of moving this code to this repo then setting up a quay build for it rather than building the image in a build config?

[accorvin]

For now, I've added the image build artifacts to this PR and updated the buildconfig to point to them.

[anishasthana]

I like that.

[HumairAK]

I think you're missing the .sops.yaml file included in the target-env folders that use sops, could you add those?

[accorvin]

I think you're missing the .sops.yaml file included in the target-env folders that use sops, could you add those?

@HumairAK Ah, good catch. I missed that when copying files over from the old PR since it's a hidden file.

Is it supposed to be in the target env directories, or just the main rsyslog directory? I've added it in this PR now in the main rsyslog directory, which looked like how it was done in other examples.

[HumairAK]

@accorvin it depends on your use case, so if stage/prod are encrypted using different gpg fingerprints then you'd use .sops.yaml for each directory (sops looks for the closest .sops.yaml in the file tree hierarchy), same if you have a different regex or other configs

In your case I see they are encrypted using the same key, so one in the top level rsyslog directory should be fine!

[sesheta]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: anishasthana, HumairAK
To complete the pull request process, please assign
You can assign the PR to them by writing /assign in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment